Selis MCP

What the Selis MCP MCP server does

Selis MCP MCP server exposes Selis transformation-management data through the Model Context Protocol. It is intended for agents that need to work with PMO entities without switching between an MCP client and the Selis application. Supported entity types include actions, risks, issues, projects, deliverables, decisions, KPIs, and objectives.

The server supports the core record lifecycle: agents can search and retrieve entities, inspect their available fields and enum values, create new records, update existing fields, and delete records. It also provides comment operations for reading threaded comments and adding a new comment or reply to an item.

How it works

The package can be launched with npx and connected to an MCP-compatible client. On the first authentication, it opens a browser for login and authorization. The resulting token is stored locally at ~/.selis/auth.json, allowing later commands to reuse the saved credentials.

Entity lookup accepts either an internal ID or a prefixed reference such as ACT-0859. Listing supports search, scope, filters, and pagination. The separate describe operation exposes the fields and PMO concepts available for an entity type, along with valid enum values that can guide create and update requests.

A command-line interface is also included. Examples in the project show commands for listing actions, retrieving an action by reference, creating a risk from supplied data, and updating an action by ID.

Setup and configuration

The quick-start command sets the Selis environment and organization before launching the package:

SELIS_ENV=dev SELIS_ORG=CalxC npx @calx/selis-mcp

For an MCP client using a .mcp.json configuration, set command to npx, pass -y and @calx/selis-mcp as arguments, and provide SELIS_ENV and SELIS_ORG in the server environment. Authentication is completed in the browser rather than through a token placed directly in the client configuration.

The repository also documents Docker deployment. Build the image, expose port 3773, and pass the Selis environment through the container. An HTTP mode is available for debugging with the dev command, an organization value, and the --http 3773 option.

Tools and capabilities

The Selis MCP MCP server exposes these MCP tools:

• selis_list searches and paginates entities using scopes and filters.
• selis_get retrieves an entity by ID or prefixed reference.
• selis_describe reports fields, PMO concepts, and valid enum values.
• selis_create creates an entity.
• selis_update changes entity fields.
• selis_delete removes an entity.
• selis_comments_list lists or threads comments for an item.
• selis_comment_add adds a comment or reply.

Limitations and notes

The provided material identifies Selis as the connected platform but does not document additional external integrations. Authentication requires an interactive browser authorization step on initial setup, and the saved credential is stored at ~/.selis/auth.json. Deletion is exposed as an MCP operation, so clients should apply their own confirmation practices before invoking it. The documented client examples are Claude Code, Codex, Cursor, and Zed, while the server is described as usable with any MCP-compatible client.