Skip to Content
MCP ServerSetup

Setup

The Asky MCP server lets you connect an AI assistant to your Asky data and ask questions in plain language. This page shows you how to connect from each tool.

You connect using the production server URL:

https://mcp.askylabs.com/mcp

You sign in with your normal Asky account in the browser. There are no tokens, keys, or secrets to copy or paste anywhere. The connection is read-only, so the assistant can read your data but can never create, change, or delete anything. For more on what is and is not allowed, see read-only access.

Pick your tool below and follow the steps.

Claude Desktop and Claude web

Works in both the Claude desktop app and Claude on the web (claude.ai). You need a paid Claude plan (Pro, Max, or Team).

On a Claude Team plan, only workspace admins can add connectors. If you do not see the option, ask an admin to add the Asky connector for your workspace.

Open your settings

Go to Settings, then open Connectors.

Add a custom connector

Click Add custom connector.

Fill in the details

Set the name to Asky and paste the server URL:

https://mcp.askylabs.com/mcp

Leave the OAuth Client ID and Client Secret fields blank. Asky registers the client for you automatically.

Add and sign in

Click Add. A browser window opens. Sign in with your Asky account, then click Approve to grant read access.

Claude Code (CLI)

Add the server

Run this command in your terminal:

claude mcp add --transport http --scope user asky https://mcp.askylabs.com/mcp

Authenticate

Run /mcp, pick asky, choose Authenticate, and sign in in the browser that opens.

Verify

Confirm the server is connected:

claude mcp list

ChatGPT

Connect Asky as a custom connector in ChatGPT’s Developer Mode. Developer Mode is required to use custom MCP servers, and is available on ChatGPT Plus, Pro, Business, Enterprise, and Edu plans. On Business, Enterprise, and Edu, a workspace admin must allow connectors first.

Developer Mode is a beta feature. Asky’s tools are read-only, so the connector can only read your data, but you should still review any connector you add before enabling it in a chat.

Enable Developer Mode

Go to Settings → Apps & Connectors (shown as Connectors on some plans). Open Advanced settings and toggle on Developer mode.

Add the connector

Back in Apps & Connectors, click Create to add a custom connector. Set the name to Asky and paste the server URL:

https://mcp.askylabs.com/mcp

Choose OAuth for authentication, and leave any client ID and secret fields blank.

Sign in

A browser window opens. Sign in with your Asky account, then click Approve to grant read access.

Enable it in a chat

Start a new chat, open the connectors menu, and turn on Asky so the assistant can use it.

Cursor

Open MCP settings

Go to Settings, then Tools and Integrations (MCP).

Add a custom MCP server

Click Add custom MCP.

Enter the details

Set the URL to https://mcp.askylabs.com/mcp and choose Streamable HTTP as the transport. When prompted, sign in with your Asky account in the browser.

VS Code (GitHub Copilot)

Create the config file

In your project, create a .vscode/mcp.json file with the following:

{
  "servers": {
    "asky": {
      "type": "http",
      "url": "https://mcp.askylabs.com/mcp"
    }
  }
}

Start and sign in

Start the server from the editor when prompted, then sign in with your Asky account in the browser.

Windsurf

Open MCP settings

Go to Settings, then MCP.

Add the server

Click Add Server and enter the URL:

https://mcp.askylabs.com/mcp

When prompted, sign in with your Asky account in the browser.

Other MCP clients

Any client that supports a remote MCP server over Streamable HTTP can connect to Asky. Add the server URL in your client’s MCP settings:

https://mcp.askylabs.com/mcp

The client opens your browser to sign in with your Asky account over OAuth. No other configuration is needed.

Verify your connection

Once you have signed in, confirm the connection works. Ask your assistant:

  • “Who am I?”
  • “List my brands”

If it answers with your Asky account and the brands in your workspace, you are connected. For more things to try, see Use Cases. For the full list of what the assistant can read, see Tools.

Troubleshooting

Leave the OAuth Client ID and Client Secret fields blank during setup. Asky registers the client automatically. Entering values here will stop the connection from working.

If the Asky tools do not appear after you connect, disconnect and reconnect the server to refresh the tool list.

You sign in with your normal Asky account in the browser. There is nothing to copy or paste, and no token, key, or secret to manage.

Still stuck? Start at the Introduction for an overview of how the MCP server works.

Last updated on
IntroductionUse Cases