Archived listing / no verified MCP endpoint/Productivity

Dutify listing

No MCP endpoint is published. This listing is retained for reference.

Dutify distributes a Claude Code and Claude.ai skill, not a released MCP server. The skill teaches an agent to discover Dutify HTTP API endpoints through the aggregated catalog, call them with an X-API-Key and self-correct on validOptions errors. It covers Hub call recordings, transcripts and Lens chat, project management, Codexum wiki and Roadmarq feature requests. The combined MCP route is described as adopted only after a separate release and tool-list verification, so there is no endpoint to configure yet.

Archived listingNo verified MCP endpoint is published. This page is retained for reference only.Source repository
Source checked Nov 12, 2026 No MCP endpoint Reviewed 2026-11-16
About

Where it fits

Dutify customers who want Claude to work with Hub, PM, Wiki and Roadmarq through the documented HTTP API.

  • Read a Hub call transcript from Claude.
  • Look up a Codexum wiki page.
  • Check Roadmarq feature requests.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
  • The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider source

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

Dutify repositoryhttps://github.com/dutifyai/dutify-cloud-ai-skill