What we build
Production-ready MCP connectors that plug directly into Claude Cowork’s admin console. Each connector includes:
- Full MCP server implementation (TypeScript or Python)
- OAuth 2.1 auth with your identity provider
- Tool + resource schemas designed for agentic use
- Audit logging compatible with Claude Enterprise admin
- Rate limiting and error handling
- Deployment to your VPC, managed cloud host, or our managed infrastructure
- Handover documentation + runbook
- 60 days of post-launch support
Connectors we’ve shipped
CRM
- Salesforce
- HubSpot
- Microsoft Dynamics
- Pipedrive
Document & content
- SharePoint (Microsoft Graph)
- Google Drive / Workspace
- Dropbox Business
- Notion, Confluence
Tickets & PM
- Jira, Linear
- ClickUp, Asana
Support & comms
- Zendesk, Intercom
- Slack, MS Teams (via Graph)
Data & analytics
- Mixpanel, Amplitude
- Looker / Looker Studio
- Snowflake, BigQuery, Postgres
Custom & legacy
- Internal REST / GraphQL APIs
- Legacy SOAP
- On-premise databases
Our MCP connector build process
Stage 1 — Scope (day 0–1)
30-minute call to confirm target system, required operations, auth model, and deployment environment. Fixed price and timeline within 48 hours.
Stage 2 — Design (day 1–2)
Tool and resource schema design, API mapping, auth flow modeling. You approve the spec before we build.
Stage 3 — Build + test (days 2–8)
Implementation, integration testing against your real system, security review, load testing.
Stage 4 — Deploy + handover (days 8–10)
Production deployment, Claude Cowork admin console integration, runbook, engineer handover call.
What makes our connectors different
AI-first schemas
We design schemas for how an agentic model will actually use them — grouping related operations, surfacing defaults, anticipating follow-on calls.
Production-grade auth
OAuth 2.1 done properly: token refresh, scope narrowing, per-user delegation, audit trail. Not a bearer-token shortcut.
Observable
Every tool call is logged with request, response, latency, and user context. You can see exactly what Claude did.
Maintained
60 days of post-launch support included. Optional retainer covers auth rotation, API version bumps, and new features.
Pricing
| Connector type | Complexity | Fixed-fee range | Timeline |
|---|---|---|---|
| Public SaaS (good API) | Low | Low four figures | 3–5 days |
| Enterprise SaaS | Medium | Mid four figures | 5–8 days |
| Microsoft Graph / SharePoint | Medium-High | Mid-to-upper four figures | 6–10 days |
| Internal API, custom auth | High | Upper four to low five figures | 7–14 days |
| Legacy / on-prem / SOAP | Very High | Low-to-mid five figures | 2–4 weeks |
Bundles: 3+ connectors quoted together come with a discount. Full pricing context →
Trusted by teams deploying Claude Cowork
“Tinkso shipped our Salesforce and SharePoint MCP connectors in 8 business days. Both passed our security team’s review on first submission. We’d budgeted a quarter for the build — we got it back.”
— VP Engineering, 600-person legal services firm
“The internal API connector was the one we were scared of. Custom auth, weird schema, 40 endpoints. Tinkso scoped it, priced it, shipped it in 10 days.”
— CTO, Series C FinTech
FAQ
Tell us about the system you need connected.
30-minute scoping call. Within 48 hours you get a fixed price and timeline.