Odyssey MCP Server — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Odyssey task, memo and timeline management: Do account-bound edits preserve the same task and timeline semantics across supported coding clients?

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

Best fit

Manage Odyssey tasks, notes, projects and timeline entries from an MCP client.

What we know

Published Odyssey365 MCP package whose registry description states that MCP-compatible clients can manage Odyssey tasks, memos/notes, projects and timeline data.

Maintenance / activity evidence

@odyssey365/mcp-server 0.6.4 published 2026-07-09T10:04:23.414Z

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

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Permissions not yet verified. Complete write authority is not verified.
Authentication not yet verified.
Sensitive access: Personal/work notes, Tasks/projects/timeline

Productivity data is sensitive and likely mutable; insufficient first-party detail for automatic write claims.

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

All limitations / Review context

Do account-bound edits preserve the same task and timeline semantics across supported coding clients?

The bounded review of the publisher's documented Odyssey task, memo and timeline management 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.

Productivity data is sensitive and likely mutable; insufficient first-party detail for automatic write claims.
Tasks/notes/projects/timeline are potentially private personal/work data; provider handling unresolved.
Sensitive access: Personal/work notes, Tasks/projects/timeline
Complete write authority is not verified.
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.
official docs/repository
authentication
exact tool inventory
write/delete semantics
retention/privacy
Only the npm profile/registry description was available in this research pass.
Exact auth, install command semantics, data retention, destructive operations and repository identity remain unresolved.

Original activity observations

@odyssey365/mcp-server 0.6.4 published 2026-07-09T10:04:23.414Z

Technical identity

npm/@odyssey365/mcp-server

Exact implementation source: https://www.npmjs.com/package/@odyssey365/mcp-server ↗
Reviewed resource type: MCP Server
Package identity: npm:@odyssey365/mcp-server

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 metadata ↗
@odyssey365/mcp-server
Recorded package identity, distribution or download evidence.
Evidence source ↗
www.npmjs.com/~odyssey365app
Source material retained for this review.
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
Publisher supplies `uninstall` command; hosted OAuth endpoint also available. Installer modifies client configuration.
publisher install or stdio launch · Publisher instructions
npx -y @odyssey365/mcp-server@latest install
Configure / authenticate
MCP100 setup guide
Odyssey offers hosted remote OAuth or local npm client; only local method installs package, may edit multiple client MCP files.
Check connection
Suggested check
After publisher odyssey-mcp installer configures client, inspect non-mutating task/note listing only; do not create tasks.
Remove / uninstall / revoke
MCP100 setup guide
If you added this integration to Claude Code under the registration name `odyssey365`, run `claude mcp remove odyssey365` to unregister that client entry. In Claude Desktop, Cursor, VS Code or another host, delete/disable the corresponding named MCP registration in that host's settings and restart/reconnect. If you installed an npm package globally or operate a separate HTTP server, uninstall/stop it with its original deployment method. This does not delete user data or revoke service credentials.
MCP client unregister, stopping hosted processes, package uninstall, OAuth disconnect and token revocation are distinct actions.
A claude mcp remove command is only valid for Claude Code when the local registration actually has that name. Other MCP hosts require their own UI/config cleanup.
Separate provider credential revocation · publisher documented: Odyssey app → Settings → MCP integration → API Key management issues keys; official README references revokedAt enforcement and rejecting revoked keys. The exact UI deletion click is not stated; no claims about its wording.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove odyssey365

Official Documentation & Sources

What it does

Published Odyssey365 MCP package whose registry description states that MCP-compatible clients can manage Odyssey tasks, memos/notes, projects and timeline data.

Capability: Productivity & Collaboration
Resource type: MCP Server
Best fit: Manage Odyssey tasks, notes, projects and timeline entries from an MCP client.

Representative uses

Manage tasks
Manage notes/memos
Manage projects
Manage timeline entries

Limitations

Only the npm profile/registry description was available in this research pass.
Exact auth, install command semantics, data retention, destructive operations and repository identity remain unresolved.

Reviewed access

Access & risk

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

Authentication: Not documented in the reviewed sources
Permissions: Not documented in the reviewed sources
Data handling: Tasks/notes/projects/timeline are potentially private personal/work data; provider handling unresolved.
Cost: unknown
Risk and cautions: Productivity data is sensitive and likely mutable; insufficient first-party detail for automatic write claims.

Access scope and cautions

Write actions: Not verified
Sensitive access: Personal/work notes Tasks/projects/timeline
Risk level: high

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

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 available discovery description lists: Manage tasks; Manage notes/memos; Manage projects; Manage timeline entries. These descriptions do not establish a fully verified tool inventory.

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority.

What data-handling boundary should I consider?

Tasks/notes/projects/timeline are potentially private personal/work data; provider handling unresolved. Recorded sensitive-access context: Personal/work notes; Tasks/projects/timeline.

What limitations and risks should I check before use?

Productivity data is sensitive and likely mutable; insufficient first-party detail for automatic write claims. Only the npm profile/registry description was available in this research pass. Exact auth, install command semantics, data retention, destructive operations and repository identity remain unresolved. 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.