MCP server
Connect Claude, Claude Code and other MCP clients to Improve, with every agent API operation as a tool.
Improve runs a Model Context Protocol server at https://improve.obelism.studio/mcp. Its tools are the agent API: list organizations, create audiences, flags and tests, read results, and manage tokens, origins and members. A tool runs exactly like the matching API call, with the same checks and errors.
Connect
Add the server URL to your MCP client. The client opens Improve in your browser, you sign in with your Improve account and allow the connection, and the client is connected. There is nothing to copy.
In Claude Code:
claude mcp add --transport http improve https://improve.obelism.studio/mcpIn Claude or other apps with connectors, add a custom connector with the same URL.
The sign-in uses OAuth 2.1 as the MCP authorization spec describes: the server's 401 points to /.well-known/oauth-protected-resource/mcp, the authorization server metadata is at /.well-known/oauth-authorization-server, and clients register with a Client ID Metadata Document or, for older clients, Dynamic Client Registration. PKCE is required.
Access
When you allow a connection, the app gets access to every organization you belong to, as far as your role in each allows. It can ask for one of two scopes:
| Scope | Tools |
|---|---|
improve:read | Only the read-only tools: listing and reading organizations, tests, results |
improve:write | Every tool, including creating, changing and deleting |
Access tokens last an hour and the app renews them on its own. The connection ends after 30 days without use, and always after 90 days. To disconnect an app sooner, open Connected apps on your account page.
The agent API's own bearer tokens don't work on /mcp: it only accepts the access tokens its sign-in issues.
Tools
There is one tool per agent API operation, named after its operationId in the OpenAPI spec: listOrganizations, createTest, getTestResults and so on. Path parameters such as organizationId and environment are tool arguments next to the body fields.
Signing up, signing in and out, password changes and resets, and applying for access are not tools: they happen in the browser, and signing out or changing the password would end the session the connection belongs to.
Read-only tools are marked readOnlyHint, and deleting or regenerating a token is marked destructiveHint, so clients can ask before running them. A failed call returns the API's problem details as the tool result, with a code and a hint.