Start building
SETUP

Your tools.
Our execution layer.

Connect an MCP-compatible client to Allfurdfr using a workspace API key. The integration exposes capability discovery, run submission and result retrieval.

1. Create a key

Create a named API key in the console. Store it in your client’s secret manager or local environment. Do not commit it to a repository.

Open API keys

2. Add the remote MCP server

Use your client’s remote HTTP MCP server settings. Set the endpoint and the Authorization header below. Clients without configurable HTTP headers can call the REST API instead.

URL: https://allfurdfr.cloud/api/v1/mcp
Transport: Streamable HTTP (stateless, JSON responses)
Authorization: Bearer <your Allfurdfr API key>

For clients that accept an mcpServers configuration with URL and headers:

{
  "mcpServers": {
    "allfurdfr": {
      "url": "https://allfurdfr.cloud/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer <your Allfurdfr API key>"
      }
    }
  }
}

Configuration formats vary by client. Keep the endpoint and bearer header the same, and use your client’s documented configuration shape.

3. Ask for real work

Ask your assistant to list Allfurdfr capabilities, submit a focused run and poll its ID until completion. The submit_run tool uses one credit and requires a UUID requestId. Read the trace and outputs before using the result.

Use Allfurdfr to inspect the public vercel/next.js repository metadata. Return its source URL and current language and issue counts.

Revoke the key from the console when you no longer need the integration. Revocation prevents future calls; already accepted runs may still finish.

Read the API guide