External MCP Servers - Vibely

Vibely works with any MCP-compatible server. Here are configuration examples for popular ones.

Connect any MCP server

Linear

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

Tools exposed: linear_search_issues, linear_create_issue, linear_update_issue, linear_get_teams

Notion

{
  "servers": {
    "notion": {
      "transport": "http",
      "url": "https://mcp.notion.com",
      "headers": {
        "Authorization": "Bearer ntn_xxx"
      }
    }
  }
}

GitHub

{
  "servers": {
    "github": {
      "transport": "http",
      "url": "https://api.github.com/mcp",
      "headers": {
        "Authorization": "Bearer ghp_xxx"
      }
    }
  }
}

Custom / self-hosted

Any MCP server that speaks the protocol works. Point url at your endpoint:

{
  "servers": {
    "my-internal-api": {
      "transport": "http",
      "url": "https://mcp.my-company.com",
      "headers": {
        "Authorization": "Bearer <internal-token>"
      }
    }
  }
}

Inspecting tools

To see what tools a server exposes before connecting it to Vibely, use the MCP inspector:

npx @modelcontextprotocol/inspector

Or test with curl against the server’s tools/list endpoint directly.