How to integrate Specific MCP with Grok Build

Connect Grok Build to Specific MCP. Summarize top objections from last week’s calls, list sales calls needing follow-up actions, and more from your terminal, with authentication handled for you.

Specific logoSpecific
Api Key

Specific is a sales call analytics platform that helps teams understand call performance. Unlock actionable insights to drive revenue and improve sales outcomes.

18 Tools

How to integrate Specific MCP with Grok Build

Grok Build is xAI's terminal coding agent. It runs on Grok 4.5, plans its work before it acts, and can run multiple sub-agents in parallel. It also reads Claude Code's MCP configuration, so any server you already have in a .mcp.json is picked up with no changes.

In this guide, I will show you how to connect your Specific account to Grok Build through Composio, so it can summarize top objections from last week’s calls, list sales calls needing follow-up actions, generate call analytics report for your team, and more without leaving the terminal. Composio holds the OAuth tokens for you, and Grok Build only calls the tools you approve.

Also integrate Specific with

Why use Composio over a standalone MCP server?

  • Read and write access. Composio's Specific integration lets Grok Build take real actions like creating drafts, sending updates, and labeling records, not just reading data.
  • 1,000+ SaaS toolkits out of the box. One endpoint gives you a full catalog of pre-built connectors, from Gmail and Slack to Notion, Linear, and Salesforce.
  • One MCP server for every app. Wire up a single Composio server instead of maintaining a separate MCP entry for each app.
  • Smart, context-aware tool loading. Grok Build caps how many tools it holds in a single request. Composio loads only the tools a task needs, so you do not spend that budget on tools you are not using.
  • Cross-app automation. Chain actions across apps in one run. Pull a thread, summarize it in Notion, and post the highlights to Slack from a single prompt.

Prerequisites

  • Grok Build installed and signed in. Install with curl -fsSL https://x.ai/cli/install.sh | bash on macOS or Linux, or irm https://x.ai/cli/install.ps1 | iex on Windows PowerShell. On first launch Grok opens a browser to authenticate; for headless or CI use, set an XAI_API_KEY environment variable instead (create the key at console.x.ai).
  • Access to the Specific account you want to connect.
  • The Composio MCP endpoint. Composio's server is remote and hosted, so there is nothing to run locally and no tunnel to set up.

Step-by-step: Connect Specific to Grok Build

1. Install and verify Grok Build

Install the CLI, then restart your shell so the grok binary lands on your PATH:

bash
curl -fsSL https://x.ai/cli/install.sh | bash
which grok

On Windows, install with PowerShell instead: irm https://x.ai/cli/install.ps1 | iex. If which grok returns a path, you are set. Grok Build runs on Grok 4.5 by default; you can switch models inside the session with /model <name>.

2. Add the Composio server

Add Composio as a remote HTTP MCP server with the grok mcp add command:

bash
grok mcp add --transport http composio https://connect.composio.dev/mcp

You can also add and manage servers from inside a session. Run /mcps to open the extensions modal on the MCP tab, then add a new server and paste the Composio URL. Added this way, Grok auto-detects the name from the URL and lists the server as connect:

bash
https://connect.composio.dev/mcp
Grok Build /mcps extensions modal listing MCP servers Grok Build adding the Composio MCP server with its URL

Grok also reads Claude Code-style config, so an entry in ~/.grok/config.toml or a project .mcp.json works the same way.

3. Authenticate

Composio uses OAuth. In the /mcps modal, select the Composio server and press i to authenticate (Grok also triggers this browser flow automatically the first time it uses a Composio tool). Click Allow to authorize access. Grok stores the tokens under ~/.grok/mcp_credentials.json, and /mcps shows Composio as connected.

Grok Build prompting to authenticate the Composio MCP server Composio authorization screen with the Allow button for Grok Build

4. Start building

Ask Grok to work with your Specific account through Composio. On the first Specific action, Composio prompts you to connect the account through OAuth. Approve the scopes once, and Composio handles token refresh from there.

What you can do after connecting Specific

  • Summarize top objections from last week’s calls
  • List sales calls needing follow-up actions
  • Generate call analytics report for your team

Security + privacy notes (important)

  • Use least-privilege access. Grant only the Specific scopes you actually need.
  • Review OAuth scopes before approving. Check that the requested scopes match what you expect Composio and Grok Build to do.
  • Keep write actions human-reviewed. Grok Build proposes a plan before it acts. Leave that approval step on for actions like sending messages or editing records.
  • Keep secrets out of version control. Your XAI_API_KEY and any tokens should never be committed. Use environment variables or a secrets manager.
TOOLS

Supported Tools

Every Specific action and event your agent gets out of the box.

Create Company

Tool to create a new company record in the Specific platform.

Create Conversation

Tool to create a new conversation (survey response) in the Specific platform.

Create or Update Company

Tool to upsert a company record in the Specific platform (create if not exists, update if exists).

Create Or Update User

Tool to upsert a user record in the Specific platform (creates if not exists, updates if exists).

Create User

Tool to create a new user (contact) record in the Specific platform.

Delete Company

Tool to delete a company record from the Specific platform.

Delete Company Attributes

Tool to delete specific custom field attributes from a company record.

Delete User

Tool to remove a user record from the Specific platform.

Delete User Attributes

Tool to delete specific custom field attributes from a user record in the Specific platform.

Get My Workspace

Tool to get current workspace information for the authenticated user.

List Companies

Tool to query company records from the Specific platform via GraphQL.

List Conversations

Tool to query conversation records (survey responses) from the Specific platform via GraphQL.

List Custom Fields

Tool to query custom field definitions in the Specific platform.

List Sources

Tool to retrieve all data sources from the Specific platform.

List Surveys

Tool to retrieve multiple survey records from the Specific platform via GraphQL.

List Users

Tool to query user accounts from the Specific platform via GraphQL.

Update Company

Tool to update an existing company record in the Specific platform.

Update User

Tool to modify an existing user record in the Specific platform via GraphQL mutation.

FAQ

Frequently asked questions

A standalone Specific MCP server gives Grok Build a fixed set of Specific tools tied to that one server. The Composio Tool Router lets Grok Build load tools from Specific and many other apps on demand, based on the task, all through a single endpoint.

Yes. Grok Build ships with native MCP support. Add a server with the grok mcp add command, from the in-session /mcps modal, or by editing ~/.grok/config.toml. It also reads Claude Code-style .mcp.json files, so Grok Build discovers the tools automatically.

Yes. Grok Build has zero-migration compatibility with Claude Code's configuration, so the same Composio server entry works in both without edits.

Tokens, keys, and configuration are encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant, so your Specific data and credentials are handled to that standard.

Start with Specific.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Specific tool your agent needs.Free to start.

Start building