A hosted [Model Context Protocol](https://modelcontextprotocol.io) server that gives AI agents full access to **Nynch** — a relationship-led growth
A hosted Model Context Protocol server that gives AI agents full access to Nynch — a relationship-led growth platform for consultants and professional services firms. That is what the nynch mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
Nynch is a relationship-led growth platform that helps consultants and professional services firms turn relationships into revenue. It combines CRM, relationship intelligence, and AI-powered coaching into a single platform.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
The server publishes 14 tools. What each one is for:
read — Search, browse, and retrieve dataread-write — Read + create, update, delete recordsadmin — Full access including agent orchestrationsearch_contacts — Search contacts by name, company, or tagsget_contact_context — Full contact context: profile, interactions, activities, notes, networksearch_deals — Search deals by title, stage, or companyget_deal_context — Full deal context: stakeholders, learnings, coaching actionssearch_deals_by_inactivity — Find stalled deals with no recent activityget_pipeline_summary — Pipeline health: stage distribution, at-risk deals, upcoming closesget_next_best_actions — AI-powered recommendations for what to do nextlist_buckets — List all buckets (lists/segments)get_bucket_contacts — Get contacts in a specific bucketConfiguration is passed through the environment: YOUR_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the team communication group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Nynch's toolset — read, read-write, admin and 11 more — is a fair guide to whether it matches your workflow. It is maintained by peterod99; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| read | Search, browse, and retrieve data |
| read-write | Read + create, update, delete records |
| admin | Full access including agent orchestration |
| search_contacts | Search contacts by name, company, or tags |
| get_contact_context | Full contact context: profile, interactions, activities, notes, network |
| search_deals | Search deals by title, stage, or company |
| get_deal_context | Full deal context: stakeholders, learnings, coaching actions |
| search_deals_by_inactivity | Find stalled deals with no recent activity |
| get_pipeline_summary | Pipeline health: stage distribution, at-risk deals, upcoming closes |
| get_next_best_actions | AI-powered recommendations for what to do next |
| list_buckets | List all buckets (lists/segments) |
| get_bucket_contacts | Get contacts in a specific bucket |
| get_bucket_game_queue | Get contacts waiting to be sorted into buckets |
| log_interaction | Record a contact interaction (call, email, meeting, note) |
{
"mcpServers": {
"nynch": {
"url": "https://crcrwtjzqzinfzokianr.supabase.co/functions/v1/mcp-server",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| YOUR_API_KEY | Credential the server authenticates with. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.