Selis MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Selis project-management entity tools: Does browser authorization retain project scope across action, risk and decision edits?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Manage PMO projects, actions, risks, issues, deliverables, decisions and KPIs.

What we know

MCP server for Selis TMiS — manage PMO entities from any MCP client This profile is based on verified official documentation where listed; unresolved operational details are explicitly marked.

Maintenance / activity evidence

@calx/selis-mcp 0.2.2 published 2026-04-27T13:26:44.076Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
User/org-scoped read/write PMO access Writes: Create/update/delete PMO entities; Add comments and replies.
Interactive browser OAuth; cached local token at ~/.selis/auth.json
Sensitive access: Organization project data, OAuth token, PMO risk/issues

Potential high-impact side effects: Create/update/delete PMO entities, Add comments and replies.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Does browser authorization retain project scope across action, risk and decision edits?

The bounded review of the publisher's documented Selis project-management entity tools and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Potential high-impact side effects: Create/update/delete PMO entities, Add comments and replies.
User/org-scoped read/write PMO access
Interactive browser OAuth; cached local token at ~/.selis/auth.json
PMO records move between the MCP process and Selis service; OAuth token cached locally.
Reviewed write actions: Create/update/delete PMO entities; Add comments and replies
Sensitive access: Organization project data, OAuth token, PMO risk/issues
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
cost: plans, pay-per-call charges, and payment authorization details
Authorization depends on the Selis user/org
OAuth session token persists at ~/.selis/auth.json
HTTP debug mode is distinct from authenticated local stdio mode

Original activity observations

@calx/selis-mcp 0.2.2 published 2026-04-27T13:26:44.076Z

Technical identity

npm/@calx/selis-mcp

Exact implementation source: https://www.npmjs.com/package/@calx/selis-mcp ↗
Reviewed resource type: MCP Server
Repository identity: calx-sa/selis-mcp
Package identity: npm:@calx/selis-mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
@calx/selis-mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
GitHub repository ↗
calx-sa/selis-mcp
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
One-time browser OAuth; token persisted at ~/.selis/auth.json. Publisher provides .mcp.json example. Change example organization/environment to your own.
publisher install or stdio launch · Publisher instructions
SELIS_ENV=dev SELIS_ORG=CalxC npx @calx/selis-mcp
Configure / authenticate
MCP100 setup guide
Publisher: `SELIS_ENV=dev SELIS_ORG=CalxC npx @calx/selis-mcp` starts browser authorization; OAuth token saved to `~/.selis/auth.json`. Org/environment must be chosen for your tenant.
Check connection
Suggested check
Use published read-only status/listing operation and client tool discovery after browser authorization.
Remove / uninstall / revoke
MCP100 setup guide
For a Claude Code registration named `calx-selis-mcp`, run `claude mcp remove calx-selis-mcp`; otherwise remove the exact entry in the chosen MCP client settings and restart/reconnect. This client-host removal command is MCP100-composed from Claude Code lifecycle documentation, not a vendor-authored uninstall. With `npx`, a separate global package uninstall normally is unnecessary. Do not delete provider data or credentials by default. Publisher OAuth token is saved at ~/.selis/auth.json; deleting local auth state is separate from server-side revocation.
Client unregister, package uninstall, data deletion, and OAuth/API token/wallet permissions are distinct.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove calx-selis-mcp

Official Documentation & Sources

What it does

MCP server for Selis TMiS — manage PMO entities from any MCP client This profile is based on verified official documentation where listed; unresolved operational details are explicitly marked.

Capability: Productivity & Collaboration
Resource type: MCP Server
Best fit: Manage PMO projects, actions, risks, issues, deliverables, decisions and KPIs.

Representative uses

List/search/get Selis records
Create or update PMO entities
Delete entities and add threaded comments

Limitations

Authorization depends on the Selis user/org
OAuth session token persists at ~/.selis/auth.json
HTTP debug mode is distinct from authenticated local stdio mode

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Interactive browser OAuth; cached local token at ~/.selis/auth.json
Permissions: User/org-scoped read/write PMO access
Data handling: PMO records move between the MCP process and Selis service; OAuth token cached locally.
Cost: Not documented in the reviewed sources
Risk and cautions: Potential high-impact side effects: Create/update/delete PMO entities, Add comments and replies.

Access scope and cautions

Write actions: Create/update/delete PMO entities Add comments and replies
Sensitive access: Organization project data OAuth token PMO risk/issues
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: List/search/get Selis records; Create or update PMO entities; Delete entities and add threaded comments.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @calx/selis-mcp. Recorded transport: stdio, http_debug. Recorded environment-variable notes: SELIS_ENV; SELIS_ORG. No configuration values are supplied here. Prerequisites: MCP-capable client. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Interactive browser OAuth; cached local token at ~/.selis/auth.json

Can it modify data or perform write operations?

Documented write actions include: Create/update/delete PMO entities; Add comments and replies. Recorded permission boundary: User/org-scoped read/write PMO access

What data-handling boundary should I consider?

PMO records move between the MCP process and Selis service; OAuth token cached locally. Recorded sensitive-access context: Organization project data; OAuth token; PMO risk/issues.

What limitations and risks should I check before use?

Potential high-impact side effects: Create/update/delete PMO entities, Add comments and replies. Authorization depends on the Selis user/org. OAuth session token persists at ~/.selis/auth.json. HTTP debug mode is distinct from authenticated local stdio mode. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.