AuthenticationCopy Anchor Link

Weely developer access uses OAuth 2.1. The same access token works for MCP tools and REST. Dashboard API keys for simpler script access are coming soon.

MethodsCopy Anchor Link

Authorization: Bearer YOUR_ACCESS_TOKEN

Connect an MCP hostCopy Anchor Link

MCP clients discover Weely’s authorization server, open a browser for login and consent, then call tools with your access token. You do not need a static API key for this flow.

RequirementsCopy Anchor Link

• A Weely account
• An MCP host (Cursor, Claude Code, ChatGPT, and similar)
• MCP URL: https://dev.weely.ai/api/v1/mcp (local: http://localhost:4005/api/v1/mcp)

What happensCopy Anchor Link

1. Your MCP host connects to the Weely MCP URL.
2. You sign in to Weely (if needed) and approve the requested scopes.
3. The host receives an access token (and refresh token when supported).
4. Tools and REST calls use that Bearer token.

Cursor exampleCopy Anchor Link

{
  "mcpServers": {
    "weely": {
      "url": "https://dev.weely.ai/api/v1/mcp",
      "auth": {
        "scopes": ["mcp", "short_url:read", "short_url:write", "analytics:read"]
      }
    }
  }
}

Do not set a static Authorization header for OAuth — that skips the browser consent flow. Many hosts register themselves automatically; you usually only need the URL and scopes.

ScopesCopy Anchor Link

Request only the scopes your integration needs.

API keys (coming soon)Copy Anchor Link

Static API keys for REST (and optional non-OAuth MCP use) are not available yet. A future guide will cover creating keys in the dashboard, rotating them, and which header to send.

Until then, use MCP OAuth for agents and the same access token for REST where your scopes apply.