MCP

Connect AI assistants such as Claude, Claude Code, GitHub Copilot CLI, OpenCode and VS Code to Alviss AI through the Model Context Protocol (MCP). Learn the server URL, how sign-in works, and which clients are supported.

Alviss AI provides a remote Model Context Protocol (MCP) server. When you connect an MCP-compatible AI assistant to it, the assistant can work with Alviss AI for you, using the same access as your own account.

Availability

MCP is only available for teams that the Alviss AI staff has enabled it for. You can sign in to the MCP server from any supported client, but you can only use it with teams that have MCP enabled. To enable MCP for your team, contact Alviss AI.

Server URL

Use this URL when you add the server to your client:

https://api.alviss.io/v1/mcp

Authentication

The MCP server uses OAuth. You do not need an access token, client ID or client secret. Every supported client identifies itself with its own published client metadata, so you only need to sign in.

The first time a client connects, it opens your browser so you can sign in:

  1. Sign in with your Alviss AI account, the same way you sign in at https://app.alviss.io.
  1. Review the access the client is asking for, then click Accept.
  1. When the browser shows that sign-in is complete, close it and return to your client.

The client can then reach the projects your account can reach in teams that have MCP enabled. It can't do anything your role doesn't allow.

Anyone using a connected client acts as you in Alviss AI. Only connect clients on devices you trust, and sign out of the client when you no longer need it.

Supported Clients

ClientGuide
Claude (claude.ai, Claude Desktop)Claude
Claude CodeClaude Code
GitHub Copilot CLIGitHub Copilot CLI
OpenCodeOpenCode
VS Code (GitHub Copilot Chat)VS Code

Other MCP clients aren't supported yet. They can't sign in, even if they support remote MCP servers.

Troubleshooting

  • The client asks for a client ID or client secret: leave those fields empty. If the client won't continue without them, update it to the latest version.
  • An error says the server doesn't support dynamic client registration: your client version is too old. Update it to the latest version.
  • Sign-in works but you can't see a team or its projects: MCP may not be enabled for that team. See Availability.
  • Sign-in works but you can't see a project: make sure your account is a member of the team that owns the project. See Teams.