This is a configuration example, not a key. Generate and manage credentials in your signed-in account. Never publish a real token.
Add a server
Every server is a remote MCP endpoint over Streamable HTTP at /mcp/<server>, for example /mcp/seo for most research tasks or /mcp/search-console for your own sites' data. Your client opens the sign-in page the first time it connects.
The production origin is crakseo.com. Clients set up on an earlier domain keep working; no endpoint path changed.
{
"mcpServers": {
"crakseo-seo": {
"url": "https://crakseo.com/mcp/seo"
}
}
}Use an API key when OAuth isn't available
Create a key under Settings, API keys and send it as an Authorization: Bearer header. Keys draw on the same prepaid API credits as OAuth sign-in.
Revoke unused keys in the dashboard. Inspect permission errors explicitly instead of treating them as an empty result.
Know what a call costs
Data tools are paid per call from API credits; failed calls are free. Search Console + Bing tools are free. Per-call prices are on each server's docs page.
Paid Google indexing always returns a quote first and needs the account owner's approval.
Keep credentials out of prompts
Paste keys only into your client's settings or secure credential prompt, never into a chat. Don't send cookies, verification codes or keys into logs.
Legacy-plan workspaces also have the workspace endpoint /api/mcp for agent tools; call get_capabilities first and use only the tools it returns.
Keep exploring
Connect your site or your agent.
Join the Link Network for backlinks and indexing, or get an API key and connect an MCP client. Cancel anytime.
Get started