TL;DR
- Connect HubSpot remote MCP for HubSpot revenue records, or Dynamics 365 Sales MCP plus Dataverse for Microsoft sales insights and record operations.
- Add Reply.io for sales engagement, RichAPI for data lookup or Linked API for programmatic actions on a connected LinkedIn account. Their actions and billing are different.
- HubSpot Developer MCP is local development tooling for apps and CMS assets. It is a separate purchase decision from the remote CRM connection.
- TexAu's MCP route now redirects to RichAPI. Use the current read-only data surface and endpoint pricing rather than the older claim that all successful actions cost one credit.
- In the worked 100-account example, data consumption is $13.20 at the starter rate, but the first prepaid purchase is $100. CRM, agent access and operating labour remain separate.
What an MCP server changes for GTM
A Model Context Protocol server exposes discoverable tools to an AI client. In a revenue stack, those tools might read a deal, enrich a company, prepare a sequence or update a property. MCP standardises the interface; the underlying product still defines what is possible, who can do it and what is charged.
The useful selection question is the missing action. A research assistant needs company data. A pipeline assistant needs CRM records. An outreach operator needs sequence and inbox state. Installing every server in this list does not make those jobs clearer.
This guide compares six documented vendor surfaces, including the two distinct HubSpot servers retained from the original shortlist. It is an integration buying guide; the separate B2B data-server comparison covers deeper enrichment recipes. The examples below are implementation designs, not claims that we connected live accounts or performed production writes.
Side-by-side comparison
| Server | Useful operations | Hosting and identity | Supported commercial basis | Main limitation |
|---|---|---|---|---|
| HubSpot remote | Search/read CRM records and propose supported record changes | Vendor-hosted HTTP; OAuth with PKCE; connected user permissions | Underlying HubSpot subscription and entitlements; no separate MCP fee identified | Tool and object availability vary; Sensitive Data blocks activity and conversation access |
| Dynamics 365 Sales | Sales research, summaries, opportunity insights and drafts | Microsoft environment endpoint; Microsoft identity and configured clients | Dynamics licensing plus applicable Copilot credits | Dataverse record CRUD needs the Dataverse connection; client support differs |
| Reply.io | Contacts, sequences, inbox, tasks and Jason draft operations | Remote HTTP; scoped bearer key or broader OAuth | Live Reply subscriptions; Email Volume starts at $49/user/month annually or $59 monthly | Sends and sequence actions can execute immediately; partial batch results matter |
| RichAPI, from TexAu's current MCP route | Company/person enrichment, search, verification and signals | Remote HTTP; API key; same pool as REST | $100 for 5,000 non-expiring starter credits | Read-only data tools do not write the CRM or send outreach |
| Linked API | Searches, profile research, conversations and LinkedIn actions | Cloud browser on a connected account; API and account-identification tokens | Core $49/seat/month on annual billing; one seat per LinkedIn account | Independent third-party automation; vendor execution allowance is not a LinkedIn action guarantee |
| HubSpot Developer | Documentation, project scaffolding, builds, uploads and logs | Local CLI-backed process using developer account access | Developer tooling; model client and relevant HubSpot features separate | Not the remote revenue-record server |
These tools are complementary. HubSpot and Dynamics are alternatives according to the CRM; RichAPI and Reply serve different stages. Linked API is an optional action layer. The local HubSpot server belongs in a developer's project when building on that platform.
The six servers
1. HubSpot remote MCP server
The remote endpoint is https://mcp.hubspot.com. It supports OAuth with PKCE and respects the connected user's permissions and installation grants. Current setup uses Development → MCP Connectors. The remote server is generally available; old references to the earlier auth-app interface should not determine today's setup. Integration documentation, availability announcement.
Useful operations include searching and fetching records, inspecting properties and creating or updating supported CRM records and activities. The documented manage_crm_objects tool presents proposed changes and requires explicit confirmation. Custom objects are now documented; the old assumption that the server covers only standard contacts and deals is incomplete.
Tool availability depends on subscription, permissions and configuration. Sensitive Data accounts block activity and conversation access through MCP, and some revenue capabilities are beta. This matters when the intended job depends on notes or messages. A broader read list also does not mean every object has the same write support.
Pricing and fit: the documentation does not establish a separate MCP surcharge. Budget the underlying HubSpot features and agent client. It is the first choice for HubSpot CRM work, with the existing user's permissions determining access. It is not a reason to grant a general administrator identity to a narrow research task.
2. Microsoft Dynamics 365 Sales MCP server
Dynamics Sales exposes named sales tools, including account and lead research, outreach drafts, record summaries and opportunity insights. These are useful when the business needs sales interpretation inside its Microsoft revenue environment. Sales MCP overview.
The current Sales endpoint follows:
https://agent365.svc.cloud.microsoft/mcp/environments/<EnvironmentID>/servers/msdyn_SalesMCPServer
For record create, update and delete operations, Microsoft's connection instructions say to connect Dataverse MCP as well, at the environment's /api/mcp endpoint. They document Copilot Studio and VS Code/GitHub Copilot setup; Claude Desktop is not supported for the Sales connection at the stated documentation date. That restriction should not be transferred to Dataverse, whose own documentation lists non-Microsoft clients. Sales connection, Dataverse tools.
Pricing and fit: Sales AI tools consume Copilot credits according to feature type unless covered by a specific licence inclusion. The published map assigns account research to basic text/generative tools and record summaries to generative answers. Dataverse also has credit rules and exemptions for qualifying licences. This is not universally “free with Dynamics”. Use the existing Microsoft estate when it supplies the sales objects, identity and operating owner; avoid choosing it merely as a cheaper wrapper around another CRM.
3. Reply.io MCP server
Reply's live remote server is https://mcp.reply.io/. It exposes sales-engagement operations across contacts, sequences, inbox conversations, tasks and Jason AI SDR drafts. A scoped bearer API key is preferable where the client accepts headers; Reply describes its OAuth route as equivalent to an all-scope key. Official MCP reference.
The contract matters to the buyer. Some actions send or start outreach immediately. Contact batches can partially succeed, so a successful call is not proof that every requested record changed. Reply's REST API remains the better route for bulk imports and deep exports outside the MCP tool surface.
Pricing: the live Email Volume entry is $49/user/month billed annually, or $59 monthly, at the starting 1,000-active-contact tier. Multichannel starts at $89 annually or $99 monthly. Higher active-contact tiers and other products change the bill. The separate Headless API credit packages are labelled “Coming soon” and illustrative; they are not a current tariff. Live subscription pricing, proposed package status.
Choose Reply when the job concerns an existing Reply sequence or inbox. It is unnecessary for research that ends in a CSV, and its powerful execution tools should not be conflated with a read-only data source.
4. RichAPI MCP, reached from TexAu's current route
TexAu's /mcp route now redirects to RichAPI. The directly applicable source documents https://mcp.richapi.ai/mcp, using an API key and the same credit pool as REST. Its data tools cover company and profile enrichment, people search, signals and email/phone waterfalls. The current MCP surface is described as read-only: it does not send emails or write your CRM. Current MCP page.
That makes it a useful research layer between the account list and the CRM write step. It also resolves a material conflict with older TexAu pages that describe a wider automation surface. Do not inherit those write capabilities into the present RichAPI connection.
Pricing: Starter is a $100 prepaid purchase for 5,000 credits, which do not expire. Published endpoint rates include one credit for profile enrichment, five for email finding and two for the named email-verifier endpoint. People search is per result, while several enrichment actions are per successful call. REST and MCP use the same commercial pool. Endpoint prices and bundles.
Choose RichAPI for research and enrichment whose endpoint units you can budget. It is a poor substitute for an outreach tool when the requirement is to enrol or message prospects. Prefer the endpoint rate table over marketing worked examples when calculating costs.
5. Linked API MCP server
Linked API's own MCP server connects an assistant to a LinkedIn account through a dedicated cloud browser. It supports account actions such as lead search, profile analysis and conversations. It is an independent third-party product, not a LinkedIn-published MCP server or official partner API entitlement. MCP overview.
The vendor documents hosted remote configuration and a local package route. Authentication includes an API token plus a separate account-identification token; choosing the wrong account token can target the wrong sender. Installation and account selection.
Pricing: one seat equals one connected LinkedIn account. Core starts at $49/seat/month on annual billing; Plus starts at $74 on that basis and adds Sales Navigator actions. The vendor's unlimited workflow-execution description is an execution allowance, not a guarantee of unlimited invitations or messages on LinkedIn. Plan comparison.
Choose Linked API when programmatic account actions are central and your team owns the account-level operation. It is unnecessary for ordinary CRM preparation or email research. Do not plan volume from an invented universal daily invitation limit; the account's available actions and platform restrictions still apply.
6. HubSpot Developer MCP server
HubSpot's local Developer server helps an assistant build apps and CMS assets. It can search and fetch developer documentation, scaffold projects, upload builds and inspect development logs through CLI-backed tools. That is useful for a GTM engineer building an app card, internal extension or HubSpot-hosted interface. Developer tool reference.
Setup uses the HubSpot CLI and hs mcp setup, with CLI version 8.2.0 or higher recommended by the current guide. The setup supports installed CLI and standalone operation, including version pinning in the latter. This is a local process, with local files and the developer's authenticated platform access. Setup guide.
Pricing and fit: no separate MCP tool fee is established in the setup documentation. Budget the AI client, development time and the HubSpot features the app requires. The server reached general availability in February 2026. It is valuable when building on HubSpot, and the wrong first connection for a salesperson simply asking about open deals. Availability announcement.
A worked account-enrichment task
Suppose the team already uses HubSpot and wants to research 100 assigned accounts, add useful contact information and return an operator-reviewed change set. Use HubSpot remote MCP plus RichAPI; Reply and Linked API are optional later execution layers.
- Read the account set. Search the assigned companies and retain CRM IDs and domains. Fetch relevant records and properties. Exclude existing customers and active outreach accounts according to your business's stored rules.
- Match identities. Use the supplied domain and selected profile references. Similar names alone do not authorise a match.
- Enrich selected records. Request the required profile, email and verification data. Keep the endpoint and source references with each result. A data-tool result is not yet a CRM update.
- Prepare changes. Return account ID, contact identity, field, previous value, proposed value and supporting source. Preserve owner and suppression fields rather than replacing them with enrichment guesses.
- Write the reviewed change set. Use the supported HubSpot write operation after its proposed-change confirmation, then read the records back. Keep unmatched records in the result file and continue the known matches.
An illustrative instruction is:
Research the 100 assigned account IDs in this input.
Use HubSpot for the authoritative company ID, domain and existing fields.
Use RichAPI only for the selected data lookups.
Exclude customers and records already in active outreach.
Keep source facts separate from the proposed sales interpretation.
Prepare a change set with old and new values; do not enrol anyone in outreach.
After the reviewed write, return updated, unchanged and unmatched counts.
For a fictional A-104 at northstar.example, finding a relevant operations contact can justify a proposed contact association. It does not justify overwriting the company's owner or enrolment status. If the email finder returns no usable value, the account still gets its known company research and a missing-email status.
Use the signal-based outbound playbook to decide which accounts merit enrichment. MCP reduces integration friction; it does not fix an unqualified list.
Price the task and the purchase separately
For this editorial scenario, assume 100 successful profile enrichments, 80 successful email finds and 80 verifications through the named two-credit verifier. Failed or differently priced actions would change consumption; the calculation uses the specified successful result set.
| Data action | Rate | Consumption |
|---|---|---|
| Profile enrichment | 1 credit × 100 | 100 credits |
| Email finding | 5 credits × 80 | 400 credits |
| Email verifier | 2 credits × 80 | 160 credits |
| Total | 660 × $0.02 starter credit rate | $13.20 allocated consumption |
The first cash purchase is $100 for 5,000 credits, leaving 4,340 credits after that run. Do not describe a $13.20 allocation as a $13.20 checkout price. Also do not substitute the cheaper alternative verification endpoint without changing the task and its unit.
Assume a $20 monthly agent-client base, two minutes of review per account at $50/hour and two administration hours at $75. Review is $166.67 and administration $150. The operating allocation is therefore $13.20 + $20 + $166.67 + $150 = $349.87, excluding the existing CRM licence and any extra agent usage. On 80 usable contacts, that is about $4.37 per usable result.
The first-purchase cash view replaces the $13.20 allocation with $100, producing $436.67, or $5.46 per usable result, with unused data credits retained. These are supported purchase and consumption bases plus explicit labour assumptions, not an all-in vendor bill.
Manual work at eight minutes per account would cost $666.67. The operating allocation leaves $316.80 of potential value per run. Six setup hours at $75 cost $450, giving about 1.4 runs to recover setup on that allocation, or roughly two using the first-purchase cash difference.
Additional connections should earn their cost. A Reply Email Volume seat on monthly billing adds a supported $59 starting base when email execution is needed. Three Linked API Core seats add $147/month equivalent on annual billing, or a $1,764 annual commitment. Neither belongs in the research budget if the deliverable stops at reviewed records.
For Microsoft teams, use the documented tool categories to budget Copilot credits. Basic text/generative tools are one credit per ten responses on the response basis; generative answers are two credits. Thus 100 basic account-research responses and 100 record summaries imply 10 + 200 = 210 feature credits before other applicable meters and orchestration. Licence inclusions, token billing and other actions determine the invoice. The useful point is that a summary and a lookup are different units, not that every MCP call has one universal price. Copilot billing rates.
Deployment and permissions that affect the choice
Remote hosting removes the local server process, but not client configuration or credential ownership. Local hosting gives access to project files and development tools, while adding a runtime to maintain. Neither location guarantees a narrow permission scope.
| Connection | Decision that matters |
|---|---|
| HubSpot remote | Which user's permissions and installation grants the connector inherits |
| Dynamics Sales and Dataverse | Which environment and clients are enabled, and which connection performs record operations |
| Reply | Scoped header key versus broader OAuth; whether sequence and send tools are exposed |
| RichAPI | Allowed data actions and spend ceiling; research output needs a separate CRM destination |
| Linked API | The account-identification token selecting the sender and the actions permitted to the client |
| HubSpot Developer | Developer account, local project and build/upload tools available to the assistant |
Do not use tool hints as the only business rule. A server's “read-only” annotation helps classify tools; the client and underlying credential still determine permitted actions. Keep retrieved pages and tool results as data, separate from the human's task instructions.
For a timeout after a write, read the destination before retrying. For partial batches, report per-item outcomes. These two habits prevent a superficially successful interaction from creating duplicate contacts or silently dropping part of the job.
Where Clay and Apollo fit
Clay and Apollo now both document official MCP support. They should not be labelled undocumented on a current GTM shortlist.
Clay exposes reusable functions and workspace controls, making it attractive when the team already has a maintained enrichment recipe and wants reps to invoke it through an agent. Its MCP calls use the underlying Actions and Data Credits model. Clay MCP settings, connection guide.
Apollo's current MCP documentation includes search, enrichment and advanced contact, list, sequence and email actions. OAuth and headless master-key access have different permission implications; it is not merely a read-only search server. Apollo MCP guide.
If either is already the team's data system, use it before adding RichAPI solely for a second catalogue. The six primary entries above cover the original integration layers; these alternatives can replace the data layer according to the existing stack.
Which connections to add first
For an account or pipeline task, start with the authoritative CRM. Add the data source or engagement tool that completes that task. Two or three connections are a useful starting arrangement, not a universal ceiling.
For HubSpot research, use remote HubSpot plus the existing enrichment provider. For Microsoft sales insights, use Dynamics Sales and add Dataverse when record operations are needed. For a Reply operator, connect Reply directly to the sequence and inbox job. Add Linked API only when connected-account LinkedIn actions are a real requirement.
Keep HubSpot Developer separate for app-building work. The recommendation is to expose the smallest useful action set for the current job, with its billing units and destination understood. Add another server when it removes a specific manual step.
FAQ
Does MCP make paid product actions free?
No. The protocol is an interface. Data credits, subscriptions, licence inclusions and AI feature meters still apply. A server without a separate MCP fee can expose chargeable operations.
Which HubSpot server should I connect?
Use remote MCP for CRM records and supported account operations. Use Developer MCP for app and CMS development through local tooling. A developer building a HubSpot application may need both for different jobs.
Is Linked API an official LinkedIn server?
It is Linked API's vendor server, but an unofficial third-party connection to LinkedIn using a cloud browser. Its seat allowance does not remove LinkedIn account restrictions or create official partner API access.
Should I use MCP for a nightly bulk import?
Use MCP when an assistant needs interactive tools and interpretation. A maintained REST integration or automation is often simpler for a fixed nightly import. The existing n8n, Zapier and Make comparison covers that adjacent decision.
