Learn how to generate and manage API keys for the Particl MCP server.
All requests to the Particl MCP server are authenticated using API keys. Each key is scoped to your account and provides access to the data available on your plan.
API keys are passed as a Bearer token in the Authorization header when connecting to the MCP server. Your AI client sends this automatically based on its configuration.
Keep your key secure
Pass your key as a Bearer token in the Authorization header in your MCP client configuration:
{
"mcpServers": {
"particl": {
"type": "http",
"url": "https://particl-mcp.onrender.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_PARTICL_API_KEY"
}
}
}
}No local installation is required — the Particl MCP server runs as a hosted service. Your AI client connects to it over HTTP.
| Action | How |
|---|---|
| Enable MCP | Settings → MCP → Toggle on |
| Regenerate key | Toggle MCP off and back on to generate a new key |
| Disable MCP | Settings → MCP → Toggle off (revokes the key immediately) |
The Particl MCP server allows up to 100 requests per 60 seconds per API token. If you exceed this limit, requests will return an error until the window resets.
Most MCP tools consume export credits when returning data. Credits are shared with CSV exports in the Particl dashboard.
| Category | Tools | Cost |
|---|---|---|
| Free | search_companies, get_credit_balance | None |
| Per row | search_market_products, get_company_products, get_market_top_products, get_market_top_companies | 1 credit per row returned |
| Per call | get_company_details, get_market_pricing_analysis | 1 credit per call |
Use get_credit_balance to check your remaining credits at any time.