Skip to main content

API keys

The MCP server uses the same header-based authentication as the REST API. Each request must include an API key in the x-api-key header to verify your identity and permissions. You can create and manage API keys through the Quartr Portal. Each API key inherits the permissions of your plan, so once your plan includes the MCP server, the keys you already use for the REST API work for it as well. See Authentication under REST API for how to generate a key. API keys do not have an expiration date by default. You can delete them at any time from the “API keys” section in the portal, which immediately revokes access.

Dataset access

Your access to the MCP server and its datasets is determined by your subscription plan. The MCP server is its own product, so its access is set separately from the REST API’s, and each API key inherits it. Tools that need a dataset outside your plan are left out of the tool list, and tools that span several datasets return only the kinds and sources your plan includes. If you have purchased the correct data packages and still receive a permission error, contact your Quartr representative.