Connection Guide

How to connect Nyask from MCP clients such as ChatGPT / Claude Desktop / Cursor. Covers the single endpoint, the two auth methods (PAT / OAuth), narrowing tools with profiles, and protocol versions.

Endpoint

Point your MCP client at this single URL. The transport is Streamable HTTP — there is nothing to install locally.

Per-client setup

Any client that supports remote MCP (URL-based) connects by adding the endpoint to its config. OAuth-capable clients open a Nyask consent screen on first connect.

Claude Desktop / Cursor

Add Nyask to mcpServers in your config (claude_desktop_config.json / mcp.json). These clients support OAuth, so you do not need to write a token by hand.

{
  "mcpServers": {
    "nyask": { "url": "https://nyask.vemi.jp/mcp" }
  }
}

ChatGPT

Add the endpoint above as a custom MCP server in connector settings. Sign-in proceeds automatically over OAuth — press “Allow” on the consent screen to finish.

MCP Inspector / curl / your own client

From tools without an OAuth flow, pass a PAT in the Authorization: Bearer header. See the “Authentication” section below for how to issue one.

curl -X POST https://nyask.vemi.jp/mcp \
  -H "Authorization: Bearer nyask_pat_xxxxxxxx" \
  -H "Content-Type: application/json" \
  -H "MCP-Protocol-Version: 2025-11-25" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Authentication

There are two ways to authenticate. Either way, the set of callable tools is determined by scope.

• PAT (Personal Access Token) — a fixed token issued in portal. Use it when you wire up the connection yourself (Inspector / curl / SDK).
• OAuth 2.1 (DCR) — used automatically by capable clients such as Claude Desktop / ChatGPT for sign-in. The client manages the token for you.

Issue a PAT and connect

To connect from a tool without OAuth, issue a PAT in portal and pass it in a header.

1. Sign in to portal → open “Settings” → “Integrations”
2. Click “Issue a new token” → choose a name (e.g. "Claude Desktop") and scope (read / write)
3. Copy the shown nyask_pat_… immediately (it cannot be shown again once closed)
4. Pass it as Authorization: Bearer nyask_pat_… in your client config

If your client supports custom headers, you can write it straight into the config file.

{
  "mcpServers": {
    "nyask": {
      "url": "https://nyask.vemi.jp/mcp",
      "headers": { "Authorization": "Bearer nyask_pat_xxxxxxxx" }
    }
  }
}

See Auth / Scope for issuing, scope, and revocation details.

Optional tuning

Everything below is optional. Skip it if you just want to connect.

Narrow tools with a profile

A profile selects “which tools are exposed to the client.” For general use we recommend `task-assistant` (read/write of tasks / notes / reminders, read-only for everything else). Specify it as a query on the connection URL.

• task-assistant — Read/write needed for task management, read-only for the rest. Default for general users.
• project-ops — Everything in task-assistant plus editing workflow definitions.
• full-access — All feature groups × full CRUD (equivalent to leaving profile unset).

https://nyask.vemi.jp/mcp?profile=task-assistant

Protocol version

The MCP-Protocol-Version header accepts multiple versions at once. Clients negotiate automatically, so you normally do not need to think about it. The latest recommended version is 2025-11-25.

Where your data goes when you connect

Since you are connecting to an external AI service, understand the handling before you choose a client.

Next

• MCP Catalog — every callable tool
• Auth / Scope — issuing, authorization, revocation