MCP servers

Model Context Protocol servers give Albert outside tools: Git, a browser, a database, documentation, your company's own services. AlbertCode connects to servers that run on your computer (a local command) and servers on the web (a URL), including ones that need you to sign in.

The quickest way: connectors

Connectors is a gallery of 88 ready-made servers. Each one is added with a click and, at most, the answers it needs: a sign-in for services on the web, a folder, or a database address. Every connector in the gallery has been run for real: started or reached the way AlbertCode does it, with its tools listed and one of them called (each database connector against a real database of its kind). A connector that signs in was taken up to the service's own sign-in page: AlbertCode registered itself with the service, and the rest is your own account.

Code and repositories

Projects and work

Docs and search

Browser and testing

Frameworks

Cloud and deployment

Databases

Monitoring and analytics

Design and content

Business and payments

Utilities

Local connectors need what they run on: uv (uvx), Node.js (npx), and for some Chrome, Docker or kubectl. The gallery says which. The first start downloads the server, so it may take a minute; later starts are quick.

/mcp install postgres uri=postgresql://localhost:5432/app
/mcp install git repository=.
/mcp install mongodb uri={env:MONGODB_URI}
/mcp install linear              # then sign in: your browser opens Linear's own sign-in page
/mcp install context7            # no sign-in: up-to-date library docs straight away

A connector that signs in, such as Linear, Notion, Jira, Stripe or Sentry, needs nothing but your account: AlbertCode registers itself with the service, opens its sign-in page, and comes back connected once you approve. For example, to give Albert your Linear issues:

1. Browse connectors → Projects and work → Linear → Connect.
2. Linear's own page opens in a new tab: sign in, and approve AlbertCode.
3. Back in AlbertCode, Linear shows Connected, with its tools. Ask "What is assigned to me this week?"

A few popular services are not in the gallery yet, because the check could not show them working: Box, HubSpot, ElevenLabs and Render make you register a client by hand; Figma and Sonatype take only clients they approved; GitHub needs your personal access token to be checked. Any of them can still be added by hand: Add server, with its URL (and a client ID where it needs one).

Add any server

# A local server: a command AlbertCode starts, with its variables
albertcode mcp add docs --command "npx -y @example/docs-mcp" --env DOCS_TOKEN=xyz

# A remote server that signs you in with OAuth (a browser window opens)
albertcode mcp add tracker --url https://mcp.example.com/mcp

# A remote server that takes a header instead
albertcode mcp add search --url https://search.example.com/mcp --no-oauth --header "Authorization=Bearer xyz"

Signing in

A remote server that needs a sign-in shows Needs auth. /mcp auth <name> (or Sign in in the browser and VS Code) opens your browser to sign in; the token is kept in your system's key store and refreshed for you. /mcp logout <name> (Sign out in the browser) removes it. A server that needs a client ID registered by hand shows Needs client ID: give it as the server's OAuth client ID.

The sign-in asks only for what the server says it needs. GitLab's MCP server, for example, asks for the mcp permission alone, so that is all the sign-in page asks you to grant, even though GitLab's sign-in offers many more (administrator rights among them). To ask for something else, give the server a scope of your own in mcp.json, the file beside your credentials that holds your servers:

"tracker": {"type": "remote", "url": "https://mcp.example.com/mcp", "oauth": {"scope": "read write"}}

Managing servers

In VS Code, MCP Servers offers the same.

The sidebar's MCP chip in the browser shows how many are connected, and the terminal says when a server connects, drops or wants a sign-in. A server that drops is reconnected by itself.

Prompts and resources

Servers can offer prompts (ready-made requests) and resources (documents and data):

/mcp prompts                       # what servers offer
/github:review-pr 128              # use a prompt: /server:prompt arguments
/mcp resources                     # what servers offer
/mcp attach docs docs://api/orders # attach a resource to your next message

In the browser, MCP prompts and resources in the command palette; in VS Code, Use an MCP Prompt or Resource. A prompt's text is sent as your message, shown in full.

What a server may do

An MCP server's tools are governed like everything else:

• While Albert plans or answers questions, only tools that read are offered.
• A tool that acts (writes, sends, changes something) needs your approval: Allow in the browser and VS Code (or Allow, and stop asking), a in the terminal.
• Every call is recorded in the evidence ledger.
• A custom agent without the mcp group cannot use MCP tools at all.

Servers you add are yours, for every repository. Servers a plugin brings are named <plugin>-<name> and removed with the plugin.