Estel Docs

Appearance

Connect a client ​

Every client needs the same server URL:

text
https://mcp.estel.tech/mcp

Clients that support MCP sign-in open Estel in your browser. You sign in, review what the app is asking for and approve it. Nothing else is needed. For clients without sign-in, or for scripts, use an API key and send it as Authorization: Bearer <key>.

Before you start

MCP access is part of paid Estel plans with an active subscription. To check yours, open Settings → API & MCP in the Estel app.

Claude ​

In Claude on the web or the desktop app:

  1. Open Settings → Connectors and choose Add custom connector.
  2. Enter Estel as the name and https://mcp.estel.tech/mcp as the URL, then add it.
  3. Choose Connect. Sign in to Estel in the window that opens and approve access.
  4. In a chat, turn the Estel tools on from the tools menu.

On Claude Team and Enterprise plans, an owner may need to add the connector for the organisation before members can connect.

Claude Code ​

bash
claude mcp add --transport http estel https://mcp.estel.tech/mcp
# Then in Claude Code run /mcp, pick "estel" and choose Authenticate.
bash
claude mcp add --transport http estel https://mcp.estel.tech/mcp \
  --header "Authorization: Bearer $ESTEL_API_KEY"

Add --scope user to make Estel available in every project. If you use the API key command, Claude Code saves the key in its own configuration.

To share the server with your team without sharing a key, commit a .mcp.json to the project. Each person sets ESTEL_API_KEY in their own environment:

json
{
  "mcpServers": {
    "estel": {
      "type": "http",
      "url": "https://mcp.estel.tech/mcp",
      "headers": { "Authorization": "Bearer ${ESTEL_API_KEY}" }
    }
  }
}

Cursor ​

In Cursor Settings, open the MCP section and add a new server. Or edit ~/.cursor/mcp.json, which applies to all projects, or .cursor/mcp.json in a project:

json
{
  "mcpServers": {
    "estel": {
      "url": "https://mcp.estel.tech/mcp"
    }
  }
}
json
{
  "mcpServers": {
    "estel": {
      "url": "https://mcp.estel.tech/mcp",
      "headers": { "Authorization": "Bearer ${env:ESTEL_API_KEY}" }
    }
  }
}

With sign-in, Cursor shows a prompt to connect Estel the first time. With an API key, Cursor reads ESTEL_API_KEY from the environment it was started in.

VS Code ​

In VS Code with GitHub Copilot, run MCP: Add Server from the Command Palette and choose HTTP. Or add the server to .vscode/mcp.json:

json
{
  "servers": {
    "estel": {
      "type": "http",
      "url": "https://mcp.estel.tech/mcp"
    }
  }
}
json
{
  "inputs": [
    { "type": "promptString", "id": "estel-api-key", "description": "Estel API key", "password": true }
  ],
  "servers": {
    "estel": {
      "type": "http",
      "url": "https://mcp.estel.tech/mcp",
      "headers": { "Authorization": "Bearer ${input:estel-api-key}" }
    }
  }
}

The API key version asks for the key once and stores it securely, so it never appears in the file.

Other clients ​

Any client that supports remote MCP servers over Streamable HTTP can connect, using either:

  • OAuth 2.1 with dynamic client registration. The client discovers everything from the server URL. See How sign-in works.
  • A custom Authorization: Bearer <api key> header.

If a client only supports local (stdio) servers, bridge it with the community mcp-remote package. It handles sign-in for you:

json
{
  "mcpServers": {
    "estel": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.estel.tech/mcp"]
    }
  }
}

Test the connection ​

Ask your assistant: "Use Estel to show my account usage." It should call get_account_usage and report your plan, credits and quotas.

To debug outside an assistant, the MCP Inspector shows every request and response:

bash
npx @modelcontextprotocol/inspector

Choose Streamable HTTP, enter the server URL, then either run the OAuth flow or add an Authorization header with an API key.

The server is stateless and answers plain JSON, so you can also call it directly:

bash
curl https://mcp.estel.tech/mcp \
  -H "Authorization: Bearer $ESTEL_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_account_usage","arguments":{}}}'

If something goes wrong, see Errors.