# Magnus [Health: Active]

**Category:** 🏢 Workplace & Productivity  
**Repository:** https://getmagnus.co/mcp  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 1  
**Directory Page:** https://allmcps.com/mcp/magnus

## Description
Remote MCP server for Magnus, an AI chief of staff for founders. Connect any OAuth-capable MCP client (Claude.ai, Claude Desktop, Claude Code) to https://getmagnus.co/mcp and your agent can work with your Magnus goals, documents, reminders and connected services (Google, Slack, GitHub, Notion), and ask Magnus to act for you. OAuth sign-in with PKCE, or a personal bearer token.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "magnus": {
    "url": "https://getmagnus.co/mcp"
  }
}
```

## Documentation

## What Magnus MCP server does

The Magnus MCP server exposes Magnus through a remote Model Context Protocol endpoint for AI agents. Magnus is positioned as an AI chief of staff for founders, and the connection lets an agent work with Magnus goals, documents, and reminders.

The server also provides access to services connected to Magnus, including Google, Slack, GitHub, and Notion. Agents can use the available Magnus capabilities to retrieve or manage this information and ask Magnus to act on their behalf.

This fits the Workplace & Productivity category for workflows that combine planning, reference material, reminders, and activity across connected work services.

## How it works

Magnus is accessed as a remote MCP server at `https://getmagnus.co/mcp`. An MCP-compatible client connects to that endpoint, then authenticates before using the exposed capabilities.

Two authentication paths are described. Clients can sign in through OAuth with PKCE, or users can provide a personal bearer token. The OAuth option is relevant for clients that support the authorization flow; the bearer-token option provides an alternative when a personal token is available.

Once connected and authorized, an agent can work with Magnus data and connected services through the MCP interface.

## Setup and configuration

Configure an MCP client to use the remote URL `https://getmagnus.co/mcp`. The client must support MCP and be able to authenticate with the server. The listed client examples are Claude.ai, Claude Desktop, and Claude Code.

During setup, use OAuth sign-in with PKCE when supported by the client. Alternatively, configure a personal Magnus bearer token according to the client’s authentication settings.

After authentication, confirm that the client can reach Magnus before relying on the connection for goal, document, reminder, or connected-service workflows.

## Tools and capabilities

The documented capability areas are:

- Work with Magnus goals.
- Work with Magnus documents.
- Work with Magnus reminders.
- Use connected Google, Slack, GitHub, and Notion services.
- Ask Magnus to act for the user.

These descriptions identify the supported areas but do not define the exact tool names, input fields, write operations, permissions, or service-specific limits. Review the client’s tool presentation and Magnus account permissions before building an automated workflow.

## Limitations and notes

The available information does not include a README, detailed API documentation, a tool inventory, licensing information, or compatibility details for clients beyond Claude.ai, Claude Desktop, and Claude Code. It also does not state whether every connected service supports the same operations.

The Magnus MCP server requires a reachable remote endpoint and authentication. OAuth with PKCE depends on client support, while bearer-token use requires a personal token. Treat the token as sensitive credential material and follow the authentication controls provided by the client and Magnus.

_Full upstream README: https://allmcps.com/mcp/magnus/readme_

