Connecting MCP Servers - Vibely

Connecting MCP Servers

Configuration file

MCP servers are configured in .mana/mcp.json at the project root (or set MCP_CONFIG_PATH to point at a different file).

{
  "servers": {
    "<server-name>": {
      "transport": "http",
      "url": "https://...",
      "headers": {}
    }
  }
}

Each server entry needs:

Field	Required	Description
`transport`	Yes	`stdio`, `http`, or `url`
`command`	stdio only	Executable path
`args`	stdio only	CLI arguments
`url`	http/url	Server endpoint
`headers`	optional	HTTP headers sent with every request

Example: Linear MCP

{
  "servers": {
    "linear": {
      "transport": "http",
      "url": "https://mcp.linear.app",
      "headers": {
        "Authorization": "Bearer lin_api_xxx"
      }
    }
  }
}

Example: Local stdio server

{
  "servers": {
    "my-tools": {
      "transport": "stdio",
      "command": "node",
      "args": ["/path/to/my-mcp-server/dist/index.js"]
    }
  }
}

Testing connectivity

Once configured, test a server with:

curl -X POST http://localhost:8100/api/v1/mcp/servers/<id>/test \
  -H "Authorization: Bearer <token>"

Or use the admin dashboard → MCP Servers → Test.

OAuth

For MCP providers that use OAuth (Notion, GitHub, etc.), Vibely handles the OAuth flow:

Admin registers the provider
User initiates OAuth from the dashboard
Vibely stores the access token and injects it into MCP requests