Polytomic provides a hosted MCP server for LLM agents and other MCP-compatible tools that need to explore and use the Polytomic API.
Use this when you want an agent to discover the right Polytomic endpoints and make API calls without hard-coding paths by hand.
Use the production endpoint:
The Polytomic MCP server exposes two tools:
search - discover Polytomic API paths, methods, parameters, pagination, and auth requirements.execute - make Polytomic API requests through the MCP server.For most agent workflows, the agent should use search first and execute second.
Most MCP-compatible agents let you register a server with a URL and headers.
If your agent supports environment variable interpolation, you can keep the API key out of the config file. The exact syntax depends on the agent, but the setup usually looks like this:
Recommended local environment variables:
AuthorizationRequired.
Send your Polytomic API key as a bearer token:
X-Polytomic-Access-ModeOptional. Defaults to read-only.
Supported values:
read-only - safest default for discovery, inspection, and read operations.full-access - allows the agent to create, update, and delete resources as well.Example:
Only use full-access when you want the agent to be able to create, update, or delete resources on your behalf.
X-Polytomic-Auth-ModeOptional. Defaults to user.
Supported values:
user - use this with a user API key generated from the user settings page.partner - use this with a partner API key from a partner account.Example:
When you use partner, the agent can act across Polytomic organizations available to that partner account.
X-Polytomic-Partner-Org-IdOptional.
Use this when you are using partner mode and want to provide a default organization scope. Typically, this will be your partner organization ID.
Example:
The hosted MCP server is configured with headers. If your agent supports environment variables, these are the ones most users will want to define locally and reference from their agent config: