# Rezonant — AI Connector Rezonant publishes 26 MCP tools to Claude. Marketplace availability, tool surface, verification tier, and what Node8 measured against the live endpoint. Source: https://node8.ai/ai-connectors/developer-tools/rezonant/ --- [AI Connectors](https://node8.ai/ai-connectors/) · [Developer Tools](https://node8.ai/ai-connectors/developer-tools/) # Rezonant Product specs, PRDs, and tasks pulled into a coding session Listed in Claude · 26 published tools · Community-listed [Claude connector docs](https://rezonant.app/content/blog/introducing-rezonant-mcp) [rezonant.app](https://rezonant.app/) Overview ## What Rezonant does Rezonant is where a product team writes specifications and PRDs, gathers context around them, and generates tasks. The connector closes the distance between that upstream work and the code: projects, specs, PRDs, tasks, and product context can be pulled into a coding session, so the reasoning behind a feature travels with the request to implement it. Writes are included as well, covering creation, update, and deletion of projects, documents, and tasks, plus starting coding-agent jobs. The uses named include implementing a feature as it was scoped, picking up a spec written by somebody else, and reviewing why a feature was agreed. Twenty-six tools are published, and access runs through OAuth against a Rezonant workspace. ### Who it is for Engineers implementing features that someone else specified in Rezonant. ### Tool surface Twenty-six tools are claimed across reads of specs and writes to documents and tasks, and the OAuth gate means that division is described in the listing rather than observed here. Availability ## Where Rezonant is listed Rezonant is listed in the Claude connectors directory only. Rezonant has no app under the same domain in the ChatGPT directory; 392 of the 3,150 products here are on both marketplaces, and this is not one of them. The MCP server behind a Claude connector is usually the same server a ChatGPT app would need, so the absence is a distribution decision rather than a technical one. Claude listing ## In the Claude connectors directory Rezonant publishes 26 tools to Claude, deeper than 77.5% of the 1,253 Claude-listed connectors. The median Claude-listed connector filed under Developer Tools publishes 13, so this one runs 13 tools above its bucket's median and ranks 26th of 95 by tool count. It falls in the 21-50 tools band, which holds 20% of the Claude directory. Rezonant publishes a remote MCP endpoint. Claude connects to it over HTTP; there is nothing to install locally. Every connector in the Claude directory is remote, all 1,253 of them, so transport is not a differentiator there. Publisher Rezonant Verification Community-listed (61.5% of the Claude directory) Filed under Developer Tools Endpoint `https://api.rezonant.app/mcp` Documentation [Publisher setup docs](https://rezonant.app/content/blog/introducing-rezonant-mcp) Published tools 26 · 21-50 tools band Depth rank in Developer Tools 26 of 95 Snapshot August 2026 Rezonant is community-listed in the Claude directory, the tier 770 of 1,253 connectors sit in (61.5%). It is the default for a self-published server, and says nothing either way about quality. In the publisher's words ## How Rezonant describes it > Rezonant is where product teams shape what they're building — defining specs and PRDs, pulling in context, aligning the team, and spinning up tasks for coding agents. This connector closes the gap between that upstream work and the code. Once connected, your agent can pull the projects, specs, PRDs, tasks, and product context from your Rezonant workspace whenever you ask — so decisions made upstream carry into the build without you re-explaining them. It can also create, update, and delete Rezonant artefacts (projects, documents, tasks) and start coding-agent jobs, right from your editor. Common uses: - Implement a feature exactly as it was scoped and agreed in Rezonant - Pick up a spec you didn't write, with full context in your coding environment - Review the reasoning behind a feature before you build it - Manage tasks and documents without leaving your agent Access is secured with OAuth and scoped to the workspace and teams you authorize. Works with the free tier. Quoted from the connector's own Claude directory listing as captured in August 2026. Node8 did not write it and does not vouch for it. Nearby ## Other Developer Tools connectors ### [Postman](https://node8.ai/ai-connectors/developer-tools/postman/) API collections, environments, and workspaces from Postman Claude ### [Agent Community](https://node8.ai/ai-connectors/developer-tools/agent-community/) Member lookup and .agent name pre-registration ChatGPT ### [Agent Ready](https://node8.ai/ai-connectors/developer-tools/agent-ready/) Scores how readable a site is to AI agents ChatGPT ### [Alchemy](https://node8.ai/ai-connectors/developer-tools/alchemy/) Onchain data queries and Alchemy app management ChatGPT ### [Armature](https://node8.ai/ai-connectors/developer-tools/armature/) Inspect MCP server activity and agent sessions ChatGPT ### [API Response Cleaner](https://node8.ai/ai-connectors/developer-tools/api-response-cleaner/) Trim API responses down to requested fields ChatGPT [All 188 Developer Tools connectors](https://node8.ai/ai-connectors/developer-tools/) This is an independent catalogue entry compiled by Node8 from Rezonant's public marketplace listing as it stood in August 2026. Listing facts come from the marketplaces; the comparisons against the rest of the directory and any live-endpoint measurements are Node8's. Node8 is not affiliated with Rezonant, and inclusion here is not an endorsement. ## Want your company reachable inside ChatGPT and Claude? Node8 builds MCP servers end to end: deciding which tools are worth exposing, the authentication and permission model, the review submissions, and the onboarding that gets them used. One server serves ChatGPT, Claude, and Microsoft Copilot. [See how it works](https://node8.ai/mcp) Book a strategy session