← DocsMarkdownSign in

Connectors

Personal tokens for Cursor, Claude, and ChatGPT.

Each person creates a personal API token at https://skill.estate/connectors. Tokens look like se_… and always act as that user.

Do not share your token. Revoke it anytime on the Connectors page.

MCP URL

https://skill.estate/mcp

Optional connector / plugin icon: https://skill.estate/logo.png

Cursor

Create a token, then add .cursor/mcp.json:

{
  "mcpServers": {
    "skillestate": {
      "url": "https://skill.estate/mcp",
      "headers": {
        "Authorization": "Bearer se_YOUR_TOKEN"
      }
    }
  }
}

Claude

  1. Create a personal token.
  2. Customize → Connectors → Add custom connector.
  3. Server URL: https://skill.estate/mcp
  4. Authentication: No sign-in.
  5. Request header: Authorization = Bearer se_YOUR_TOKEN

(Request headers may require org beta access.)

ChatGPT

ChatGPT custom MCP plugins use OAuth, not a pasted static header.

  1. Add custom MCP server URL: https://skill.estate/mcp
  2. Choose OAuth.
  3. Sign in with your @micro.company Google account when Skill Estate opens.
  4. ChatGPT receives a token bound to your account.

Discovery: https://skill.estate/.well-known/oauth-protected-resource

Legacy shared token

A company-wide SKILLHUB_MCP_TOKEN may still exist for admin/automation. Prefer personal tokens. Shared token may allow an actor override header; personal tokens ignore actor spoofing.