https://mcp.eversince.ai/mcp. It uses Streamable HTTP and is stateless: every request carries its own credential, and there is no session to open or close.
Authentication
The server accepts two credentials onAuthorization: Bearer.
- OAuth 2.1. A client finds the sign-in flow through
https://mcp.eversince.ai/.well-known/oauth-protected-resource(RFC 9728) and walks the user through signing in, with nothing to paste. A user without an account can create one on the sign-in page. - An API key (
es_live_…), created in the app under Settings, API keys.
WWW-Authenticate header that points to the metadata, so a client can start the sign-in flow.
A connection starts in the workspace chosen when it was made, and can switch to any other workspace the user has given it access to (manage_settings, see Workspaces). API keys can only be created for workspaces the user owns. A member of someone else’s workspace can connect with OAuth.
Capabilities
tools/listreturns every tool with its JSON Schema input, the same list asGET /api/v1/tools.- The server’s instructions hold the operating manual: how the workspace is organized and the rules that apply across tools. The opening lines make sense on their own, so a client that reads only the start of the instructions still learns what Eversince is. A client that does not pass the instructions on can read the same manual with
manage_skillsget, idmanual. - Tools that return large results declare
anthropic/maxResultSizeChars, so a client that shortens long results keeps a skill or a batch result complete. - The server offers no resources and no prompts.
- Two tools are on the MCP server only:
get_api_session, which gives a script a credential (see Authentication), andshow_media, which returns a file as a link, and a picture also as a small preview the conversation displays.
On the user’s computer
The desktop app runs the same server on the machine it is installed on, athttp://127.0.0.1:3837/mcp (the next free port when 3837 is taken), bound to the loopback interface only and backed by the user’s own session. There is no separate sign-in. When the user connects a client in the app, the app issues that client a bearer token, and every request must carry it. Work that runs through this server on the computer is free, and files on disk can be added to the library where they are, without moving them.
eversince init --agent <name> connects Claude Code, Codex, Cursor, VS Code or Claude Desktop through the app, and opens the app if it is closed. init adds an entry to the client’s settings that runs eversince mcp --agent <name>, a stdio server in the CLI that passes the client’s token to the app. Claude Desktop gets a bundle built on the same bridge.
Naming the agent
A connection made througheversince login is registered under one OAuth client that every agent shares, so an agent can set its own name with POST /api/v1/connections/agent, using its own token. The app then shows that name to the user. init does this for the agent.
