xpna

Appearance

Connect xpna MCP ​

Notes:

xpnAI is currently in feature preview and as such documentation for this feature is still work in progress

Before connecting ​

Before a connection is created, the following should be prepared:

  • access to the xpna workspace that should be used
  • a supported MCP client, such as Claude Desktop or Visual Studio Code
  • the xpna MCP server URL: https://mcp.xpna.app/mcp

Two authentication methods are supported:

  • OAuth, which is recommended and should be used when the client supports browser-based sign-in
  • Personal Access Token, which can be used when the client allows an Authorization header to be configured manually

Connect with OAuth ​

OAuth is the recommended option for end users. The sign-in flow is completed in the browser and approval is granted directly in xpna.

Claude Desktop ​

In Claude Desktop, the xpna MCP server can be added as a remote custom connector.

  • Open Claude settings.
  • Open the connectors or custom connectors area.
  • Add a new custom connector.
  • Enter a name such as xpna.
  • Enter the server URL: https://mcp.xpna.app/mcp
  • Continue to the sign-in step when prompted.
  • Complete sign-in to xpna in the browser if a session is not already active.
  • Approve the connection for the required workspace.
  • Return to Claude Desktop and enable the connector for the conversation if needed.

Note:

Exact labels can vary by Claude plan and product release.

If the custom connector option is not available, the current Claude plan or organization settings should be checked.

Visual Studio Code ​

In Visual Studio Code, the xpna MCP server can be added through the MCP commands or by editing mcp.json.

  • Open the Command Palette.
  • Run MCP: Add Server and choose the preferred location, or open the MCP configuration file directly.
  • Add an HTTP server that points to https://mcp.xpna.app/mcp
  • Start the server if prompted.
  • Accept the trust prompt if shown.
  • Complete the xpna browser sign-in flow when prompted.
  • Return to chat after the server has connected.

The following example can be used in .vscode/mcp.json or the user MCP configuration:

json
{
  "servers": {
    "xpna": {
      "type": "http",
      "url": "https://mcp.xpna.app/mcp"
    }
  }
}

Connect with a Personal Access Token ​

Personal Access Tokens are intended for clients that allow a bearer token to be supplied manually. Where OAuth is available, OAuth should usually be preferred.

Create a Personal Access Token in xpna ​

A Personal Access Token can be created from the Access Tokens page in xpna.

  • Open xpna web.
  • Open Settings.
  • Select Access Tokens.
  • Create an MCP token for the required workspace.
  • Copy the one-time secret before leaving the page.

Full token creation and lifecycle details are provided in Access Tokens.

Use a Personal Access Token in Visual Studio Code ​

Visual Studio Code supports HTTP headers in mcp.json, so a Personal Access Token can be stored as a secure input and sent as a bearer token.

json
{
  "inputs": [
    {
      "type": "promptString",
      "id": "xpna-mcp-token",
      "description": "xpna MCP Personal Access Token",
      "password": true
    }
  ],
  "servers": {
    "xpna": {
      "type": "http",
      "url": "https://mcp.xpna.app/mcp",
      "headers": {
        "Authorization": "Bearer ${input:xpna-mcp-token}"
      }
    }
  }
}

After the configuration is saved, the server can be started from the MCP commands in Visual Studio Code.

Use a Personal Access Token in Claude Desktop ​

OAuth should usually be used in Claude Desktop when the remote connector flow is available.

If a Claude client exposes manual header configuration for a remote MCP server, the Personal Access Token can be supplied as:

  • Authorization: Bearer <token>

If manual header configuration is not offered, OAuth should be used instead.

Troubleshooting ​

  • If the MCP server cannot be added in Claude Desktop, the current Claude plan or organization settings should be checked.
  • If the sign-in prompt does not appear, the server should be removed and added again.
  • If the token secret has been lost, a new token should be created.
  • If MCP pages are not visible in xpna, feature availability or workspace access should be confirmed.

Copyright © 2025 xpna