Connect your client
You need two things:
| Value | |
|---|---|
| Server URL | https://mcp.<your-domain>/mcp (local stack: http://localhost:4780/mcp or http://mcp.apps.localhost/mcp) |
| Header | Authorization: Bearer <token>. See Authentication. |
The transport is Streamable HTTP ("type": "http" in most clients).
Until OAuth ships, only clients that let you send a custom header connect directly. The examples below use the local dev token (dev-token, or dev-token:<email> to act as someone else).
Claude
- Claude Code
- Claude Desktop
- claude.ai
claude mcp add --transport http vastframe https://mcp.<your-domain>/mcp \
--header "Authorization: Bearer dev-token"
Add --scope project to write it into the repository's .mcp.json so your whole team gets it. Check it with claude mcp list, or /mcp inside a session.
Local stack:
claude mcp add --transport http vastframe http://localhost:4780/mcp \
--header "Authorization: Bearer dev-token"
Claude Desktop's Settings → Connectors expects OAuth, which isn't available yet. Until then, bridge the server through a local process with mcp-remote, which can send a header. Edit claude_desktop_config.json (Settings → Developer → Edit Config):
{
"mcpServers": {
"vastframe": {
"command": "npx",
"args": [
"-y", "mcp-remote", "https://mcp.<your-domain>/mcp",
"--header", "Authorization: Bearer ${VF_TOKEN}"
],
"env": { "VF_TOKEN": "dev-token" }
}
}
}
Restart Claude Desktop. The vastframe tools appear under the tools menu.
claude.ai custom connectors (Settings → Connectors → Add custom connector) authenticate with OAuth and don't take a static bearer token.
claude.ai connectors will work once vastframe's OAuth server ships: you'll add https://mcp.<your-domain>/mcp as a custom connector and sign in with your company account. Your organization's Claude admin may need to allow the connector first.
GitHub Copilot
- VS Code
- Copilot Studio / Microsoft 365 Copilot
Create .vscode/mcp.json in your workspace (or run MCP: Add Server from the command palette):
{
"inputs": [
{ "type": "promptString", "id": "vf-token", "description": "vastframe token", "password": true }
],
"servers": {
"vastframe": {
"type": "http",
"url": "https://mcp.<your-domain>/mcp",
"headers": { "Authorization": "Bearer ${input:vf-token}" }
}
}
}
Open Copilot Chat in Agent mode and pick the vastframe tools from the tools menu.
In organizations on Copilot Business or Enterprise, an admin must enable the "MCP servers in Copilot" policy first.
Copilot Studio connects through dynamic client registration, and a pre-packaged Microsoft 365 Copilot declarative agent is planned so IT can roll vastframe out to every employee inside Copilot. Both depend on the OAuth server and aren't available yet.
Other MCP clients
Any client that supports remote MCP over Streamable HTTP with custom headers works. For example, Cursor:
{
"mcpServers": {
"vastframe": {
"url": "https://mcp.<your-domain>/mcp",
"headers": { "Authorization": "Bearer dev-token" }
}
}
}
Clients that only speak stdio can use the mcp-remote bridge shown in the Claude Desktop tab.
Check the connection
Ask your agent:
Call the vastframe
whoamitool.
It should answer with your name and the platform version. If you get 401 unauthorized, the token is missing or wrong.
Teach the agent the SDK
The server tells clients to call get_docs before writing app code. To make it stick, paste the AGENTS.md snippet into your repository: ask the agent to "call get_docs with topic agents and add the snippet to CLAUDE.md" (or AGENTS.md, or .github/copilot-instructions.md).