Two layers sit side by side: the plain CRM reads and writes, and the scoring that says which relationship is cooling, which deal has thin stakeholder coverage, and who to reach today. Asking what to do this morning is one call rather than a report you assemble.
A hosted server for Nynch, a relationship-led growth platform for consultants and professional services firms. 47 tools in five groups: CRM reads, CRM writes, relationship intelligence, a bounded context query layer, and multi-agent orchestration.
- Contacts and deals searched and opened in full — profile, interactions, activities, notes and network on one side; stakeholders, learnings and coaching actions on the other
- Pipeline health in a call: stage distribution, at-risk deals, upcoming closes, and the deals that have gone quiet found by inactivity
- Writes that match the reads — interactions logged, notes and tasks created, deals staged, contacts and companies created and updated, contacts soft-deleted so a mistake is recoverable
- The judgement layer: authority score across 6 dimensions, a 5-factor relationship strength score, engagement trends, at-risk relationships, deal velocity and stakeholder coverage, and a weekly briefing
- A buying committee map with roles, influence and sentiment, and contact signals — job changes, company changes, buying intent, identified website visits without page paths
- An AI-ready context briefing exported for any contact or deal, and next best actions derived rather than listed
- A context query layer that is metadata-first and never accepts raw SQL: list the sources, describe one, see its selectable columns and allowed filters, then read a bounded slice
- Multi-agent orchestration — agents registered with capabilities and archetype, a shared key-value context store with namespaces and TTLs, handoffs routed by name or capability, and heartbeats for liveness
- Three resources readable by URI: a contact, a deal, and the pipeline summary
A Nynch account and an API key created under Settings → Integrations → Claude & AI Assistants, sent as an Authorization bearer token. Nothing to install: the endpoint speaks JSON-RPC 2.0 over streamable HTTP, is stateless, and negotiates 2025-11-25, 2025-06-18 or 2025-03-26 with your client. The key's scope decides the surface — read, read-write, or admin for the orchestration tools — and the limit is 1,000 requests per hour per key.
One command plus a key — npx -y mcp-remote https://crcrwtjzqzinfzokianr.supabase.co/functions/v1/mcp-server, then supply credentials