Contextium MCP Server

What contextium-io/contextium-mcp-server MCP server does

The contextium-io/contextium-mcp-server MCP server exposes Contextium workspace data to AI assistants through MCP. A workspace can contain context libraries, files, agents, skills, workflows, tags, members, identities, and project activity. Files are versioned when updated, and deleted files or resources move to trash so they can be restored.

The server is designed for shared team context rather than a single document lookup. An assistant can load a complete workflow with its related agents, skills, files, and libraries, or search and retrieve only the resources needed for a task. Workflows can also be shared with workspace members, and team members can be notified after supported resources are created or changed.

How it works

Core tools use a resource type and, where needed, a workspace or resource ID. Use list for lightweight summaries, get for complete details, and search when the exact file ID is unknown. Search supports text across file titles and content, partial file or title matching, and tag filtering with AND behavior. Creating a file requires a library, title, and complete content; creating a workflow can associate projects, agents, skills, and tags.

Files can reference other files in the same workspace with an inline //<fileId> token. The referenced file must already exist, and Contextium indexes the link and creates the corresponding backlink. Relationship management also supports assigning skills to agents, applying file tags, and managing workflow members.

Project-oriented tools include guided or autonomous project setup, research setup, session resumption, lesson capture, idea analysis, phase management, and workflow loading. The marketplace tool can search, inspect, and install shared skills, agents, and MCP server listings. figma_sync can list connected Figma files or import design tokens, components, and page structure into Contextium libraries.

Setup and configuration

The contextium-io/contextium-mcp-server MCP server requires Node.js 18 or newer. Add it to an MCP client using the @contextium/mcp-server npm package. For Claude Desktop, configure the server with an npx command and the package name in the client’s MCP configuration file.

After adding the server, run npx @contextium/mcp-server setup. The setup flow opens a browser for login, workspace selection, and authorization. Once completed, the server should appear as running in Claude Desktop’s developer settings. The provided material does not specify environment variables or manual credential fields.

Tools and capabilities

Available capability areas include:

• Workspace CRUD for files, libraries, agents, skills, workflows, and supported resources.
• Full-text, filename, title, and tag-based file discovery.
• Workflow loading, project setup, session resumption, and phase activity.
• Version-preserving file updates and file relationship management.
• Workspace activity, archived activity, entity activity, and workflow activity records.
• Team member notifications, identities, lessons learned, and quick-note capture.
• Marketplace browsing and installation, plus Figma content synchronization.
• Contextium status and help tools for inspecting the current workspace and available capabilities.

Limitations and notes

The server operates against a Contextium workspace and requires browser-based authentication before use. Workspace permissions affect which resources are visible or can be changed. File links are limited to files in the same workspace and require real UUIDs; invented IDs create dangling links. The project capability is deprecated in favor of phase tools and load_workflow. The supplied material does not document offline operation, environment-variable configuration, or support for clients beyond the stated MCP-compatible clients.