Specific
Sales call analytics to drive revenue
Verdict
Common use cases
- Log customer feedback from Slack threads
- Create contacts during discovery calls
- Update company records after sales meetings
- Delete duplicate profiles in bulk
- Sync survey responses to CRM instantly
Integration
- Vendor
- Specific
- Category
- crm
- Auth
- API_KEY
- Tools
- 18
- Composio slug
specific
Tools
- Create Company
Tool to create a new company record in the Specific platform. Use when you need to add a new company to the workspace with optional ID, name, and custom attributes.
- Create Conversation
Tool to create a new conversation (survey response) in the Specific platform. Use when you need to add a new conversation with content, optional contacts, companies, and custom fields. Content can be a simple string or structured ProseMirro
- Create or Update Company
Tool to upsert a company record in the Specific platform (create if not exists, update if exists). Use when you need to ensure a company exists with specific data, creating or updating as necessary based on the filter criteria.
- Create Or Update User
Tool to upsert a user record in the Specific platform (creates if not exists, updates if exists). Use when you need to ensure a contact exists with specific data, merging with existing records based on email or ID.
- Create User
Tool to create a new user (contact) record in the Specific platform. Use when you need to add a new contact with email, name, and optional custom attributes or company association.
- Delete Companydestructive
Tool to delete a company record from the Specific platform. Use when you need to remove a company by its ID. The operation is permanent and returns the deleted company's details.
- Delete Company Attributesdestructive
Tool to delete specific custom field attributes from a company record. Use when you need to remove custom attributes by their keys from a company. Returns the updated company details.
- Delete Userdestructive
Tool to remove a user record from the Specific platform. Use when you need to permanently delete a contact from the workspace.
- Delete User Attributesdestructive
Tool to delete specific custom field attributes from a user record in the Specific platform. Use when you need to remove custom field values from a contact without deleting the contact itself.
- Get My Workspace
Tool to get current workspace information for the authenticated user. Use when you need to retrieve the workspace ID and name for the authenticated API key.
- List Companies
Tool to query company records from the Specific platform via GraphQL. Use when you need to retrieve company information, optionally filtering by ID or name.
- List Conversations
Tool to query conversation records (survey responses) from the Specific platform via GraphQL. Use when you need to retrieve customer feedback, survey responses, or conversation history. Returns up to 20 most recent conversations, optionally
- List Custom Fields
Tool to query custom field definitions in the Specific platform. Use when you need to retrieve available custom fields that can be associated with companies, contacts, or conversations. Optionally filter by entity type.
- List Sources
Tool to retrieve all data sources from the Specific platform. Use when you need to fetch available sources in the workspace.
- List Surveys
Tool to retrieve multiple survey records from the Specific platform via GraphQL. Use when you need to fetch all available surveys with their metadata, including names, contexts, tones, and associated conversation data.
- List Users
Tool to query user accounts from the Specific platform via GraphQL. Use when you need to retrieve user information, optionally filtering by ID, email, or custom attributes.
- Update Company
Tool to update an existing company record in the Specific platform. Use when modifying company name or custom attributes.
- Update User
Tool to modify an existing user record in the Specific platform via GraphQL mutation. Use when you need to update contact information such as name, email, company association, or custom attributes.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Click 'Add MCP Integration' and select Specific from the list. 3. Log into your Specific account in a separate tab and go to Settings > API Keys to generate a new key with write permissions for contacts, companies, and conversations. 4. Copy the API key and paste it into the Switchy connection form, then click 'Connect'. 5. Switchy will verify the key and confirm the connection — you'll see a green checkmark when it succeeds. 6. Open any Space and type '@Specific create a contact named Alex Chen with email alex@example.com' to test the integration. 7. Check your Specific workspace to confirm the contact appears — if it does, the MCP is live and ready for your team to use.
What teammates see: by default, memories from Specific are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Create Contact from Email
@Specific create a user with email jordan@acmecorp.com, first name Jordan, last name Lee, and associate them with the company Acme Corp.Open in a Space →
Log Survey Response
@Specific create a conversation with content 'Customer reported slow load times on mobile app' and link it to contact email sam@widgets.io with tag 'bug-report'.Open in a Space →
Update Company Details
@Specific create or update a company named Beta Industries with custom attribute 'plan_tier' set to 'enterprise' and 'renewal_date' set to '2025-06-01'.Open in a Space →
Bulk Delete Outdated Contacts
@Specific delete the user with ID usr_abc123xyz and confirm the record is permanently removed from the workspace.Open in a Space →
Remove Custom Attributes
@Specific delete the custom attributes 'legacy_score' and 'old_segment' from the company with ID comp_456def.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@specific pull all companies created in the last 30 days and show me which ones have no assigned account owner
Found 47 companies created since January 15. Of those, 12 have no assigned account owner: Acme Industries (created Jan 18), BlueSky Logistics (Jan 22), Cascade Partners (Jan 29), and 9 others. The unassigned companies span three industries: 5 in manufacturing, 4 in logistics, 3 in professional services. All 12 have at least one conversation logged but no follow-up activity in the past week. This suggests they may be stalled leads that need immediate owner assignment.
This example shows the MCP's ability to filter and aggregate company records by date and custom field values. Requires read access to company data and custom attributes. The response shape depends on your workspace's custom field schema—if 'account owner' isn't a tracked attribute, the query won't return meaningful results.
@specific create a new contact for sarah.chen@techcorp.io, associate her with TechCorp's company record, and tag her as 'enterprise-tier' in the CRM
Created contact Sarah Chen (sarah.chen@techcorp.io) and linked to TechCorp (company ID: cmp_8x3k9). Applied custom attribute 'customer_tier: enterprise-tier'. The contact now appears in TechCorp's contact list and will inherit any company-level automation rules you've configured for enterprise accounts. Note: If a contact with this email already existed, the MCP would have updated the existing record instead of creating a duplicate.
Demonstrates the create-or-update pattern that prevents duplicate contacts. The MCP merges by email, so repeated runs with the same address won't clutter your workspace. Requires write permissions for both users and companies. Side-effect: This action may trigger downstream automations (welcome emails, Slack notifications) if you've configured them in Specific.
@specific review all conversations from the past week where customers mentioned 'pricing' or 'discount', then draft a summary of common objections for our sales team
Analyzed 23 conversations containing pricing keywords. Three recurring objections emerged: (1) 'Annual contract too long'—8 mentions, mostly from SMB segment asking for quarterly billing. (2) 'Feature parity with competitors'—6 mentions, specifically comparing your Analytics tier to Competitor X's base plan. (3) 'Onboarding cost concerns'—5 mentions, with customers requesting included implementation hours. Recommended talking points: Emphasize ROI timeline for annual plans, create a feature comparison sheet for Analytics, consider bundling 10 hours of onboarding into enterprise deals.
Shows how the MCP's conversation search pairs with AI reasoning to surface patterns across customer feedback. The MCP retrieves raw conversation content; the AI synthesizes themes. Accuracy depends on how consistently your team logs conversations in Specific. If most customer interactions happen outside the platform (email, calls), this analysis will miss them.
Use-case deep-dives
When Specific MCP saves manual CRM entry after discovery calls
A 3-person sales team runs 8-12 discovery calls per week and logs notes in Notion or Google Docs. The Specific MCP is the right call here if you're already using Specific as your CRM and want to skip the copy-paste ritual. After each call, the team can use Create Or Update User to ensure the contact exists with the right email and company, then Create Conversation to log the demo notes and next steps. The upsert logic means you won't duplicate records if someone was already in the system. The trade-off: if your team is still shopping for a CRM or uses Salesforce, this MCP won't help—it only talks to Specific's API. If you're committed to Specific and tired of manual data entry after calls, this is a 10-minute setup that pays off by week two.
How Specific MCP handles survey responses from 50+ customers per week
A 6-person support team collects NPS surveys and feature requests through Typeform or email, then manually tags and routes them in Specific. The MCP's Create Conversation tool is built for this: it accepts survey content, links it to existing contacts or companies, and applies custom fields for routing. If your team processes more than 30 feedback items per week, the MCP can automate the ingestion step—no more copying survey responses into Specific by hand. The boundary: if your feedback volume is under 20 per week, the manual flow is probably faster than writing the automation. And if you need to enrich contacts with data from other tools (like Clearbit or LinkedIn), you'll need a second MCP in the chain. For teams drowning in survey data and already using Specific, this cuts triage time by half.
When Specific MCP is overkill for one-time CRM hygiene
A 2-person ops team needs to delete 200 duplicate company records and scrub outdated custom fields from another 150 accounts. The Specific MCP has Delete Company and Delete Company Attributes tools, but this is a borderline case. If the cleanup is a one-time project, you're better off using Specific's bulk actions in the UI or exporting to CSV and re-importing. The MCP shines when cleanup is recurring—say, you run a monthly script to remove test accounts or expired trial companies. At that cadence, the 18 tools give you programmatic control without writing a custom integration. The threshold: if you're doing this once, skip the MCP. If it's monthly or triggered by another workflow (like a Stripe webhook), the MCP is the right layer. For one-off hygiene, the UI is faster.
Frequently asked
What does the Specific MCP do in Switchy?
It lets AI agents create, update, and delete customer records (contacts and companies) in your Specific workspace. The MCP can also log survey responses as conversations and manage custom field data. Use it when you want AI to maintain your CRM automatically based on chat context or external triggers.
Do I need admin access to connect Specific?
You need a Specific API key with write permissions to companies, users, and conversations. Specific doesn't use OAuth — you generate the key in your workspace settings. Anyone with API key access can connect it, but limit this to team members who should modify customer data.
Can the Specific MCP search existing contacts or pull conversation history?
No. The 18 tools focus on creating, updating, and deleting records. There's no search or read-only query tool. If you need to check whether a contact exists before creating one, use the Create Or Update User tool — it merges with existing records automatically.
Why use this instead of Specific's native API?
The MCP wraps Specific's API in natural-language tools AI agents can call directly. You skip writing integration code and handling auth refresh logic. The trade-off: you're limited to the 18 exposed tools. For bulk imports or custom workflows, hit the API yourself.
Who on the team should connect Specific to Switchy?
Whoever owns your CRM data hygiene. The MCP can delete records permanently, so treat the API key like admin credentials. If multiple people need AI-assisted CRM updates, share one Switchy workspace connection rather than issuing separate keys.