Connect AgentSEO

Choose your setup

Use a server-side AgentSEO API key with no allowed domains. Analysis tools can consume credits and create jobs; repeated calls can incur another charge.

Setup

1. Create a server-side API key

   Keep the key private and supply it through AGENTSEO_API_KEY in the environment inherited by your client. Do not paste it into shared project configuration.

   Open AgentSEO API keys

   Step sources

   • raw.githubusercontent.com — reviewed 2026-11-14
   • www.agentseo.dev — reviewed 2026-11-14

2. Add the server to your client

   Set AGENTSEO_API_KEY privately in your client environment. The example contains an environment reference, never a credential.

   .mcp.json

   {
     "mcpServers": {
       "agentseo": {
         "type": "http",
         "url": "https://www.agentseo.dev/mcp",
         "headers": {
           "Authorization": "Bearer ${AGENTSEO_API_KEY}"
         }
       }
     }
   }

   Step sources

   • code.claude.com — reviewed 2026-11-14

3. Share configuration, not credentials

   Commit the project configuration after reviewing it. Each teammate supplies their own credentials or authorization and approves the project server in their client.

   Step sources

   • code.claude.com — reviewed 2026-11-14

4. Inspect the available tools first

   Connect and inspect the tool list. Choose a small task only after reviewing its credit cost and inputs. No paid analysis call was performed for this guide.

   Step sources

   • raw.githubusercontent.com — reviewed 2026-11-14

5. If connection fails

   Check that your client inherited AGENTSEO_API_KEY and the key is a server-side key with no allowed domains. Review account credits before running analysis.

   Step sources

   • raw.githubusercontent.com — reviewed 2026-11-14

What has been verified

Documentation reviewed

reviewed · 2026-11-14

Official setup documentation reviewed for these selected combinations. Runtime observations below are separate.

Endpoint response

Not tested for this guide revision

Authentication completed

Not tested for this guide revision

Tool call succeeded

Not tested for this guide revision

An endpoint response, including HTTP 401, does not establish successful authentication or tool execution.

Evidence and revisions

Reviewed 2026-11-14. Instructions are bound to the provider record and selected client recipe.

Publisher documentation

Check these sources for current account requirements and client support before connecting.

• github.com/AgentSEO-dev/agentseo-clients
• www.agentseo.dev/docs/api-reference