Model Context Protocol (MCP) server for Apollo.io API integration
Force is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
A simple MCP server with packaged tools, for each Salesforce API (REST, Tooling, GraphQL, etc.)
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user force-mcp '--' npx -y @rapidocloud/mcp-force
# 2 — ask your agent for something these tools do
# tooling_search, run_tests_sync, tooling_run_tests_async and 75 more
Force costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Force as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user force-mcp '--' npx -y @rapidocloud/mcp-forceReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
78 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Perform a tooling search in Salesforce.
No parameter schema on file.
Run tests synchronously in Salesforce Tooling API.
No parameter schema on file.
Run asynchronous tests in Salesforce Tooling API.
No parameter schema on file.
Executes a query against an object using the Salesforce Tooling API.
No parameter schema on file.
Execute Apex code anonymously on Salesforce.
No parameter schema on file.
Retrieve available code completions for Apex system method symbols.
No parameter schema on file.
Create a new Tooling SObject in Salesforce.
No parameter schema on file.
Get tooling metadata for a specific Salesforce SObject.
No parameter schema on file.
Lists the available Tooling API objects and their metadata.
No parameter schema on file.
Get the tooling describe of a Salesforce SObject.
No parameter schema on file.
Access records from Salesforce.
No parameter schema on file.
Query Salesforce records using SOQL (Salesforce Object Query Language).
No parameter schema on file.
Set, reset, or get information about a user password in Salesforce.
No parameter schema on file.
Retrieve suggested Salesforce Knowledge articles for a specified SObject.
No parameter schema on file.
Set, reset, or get information about a user password in Salesforce.
No parameter schema on file.
Access Salesforce records based on the specified object ID.
No parameter schema on file.
Delete a record from a specified Salesforce SObject.
No parameter schema on file.
Creates or updates records in Salesforce based on external ID.
No parameter schema on file.
Retrieve image data from a rich text area field in a Salesforce record.
No parameter schema on file.
Access SObject relationships in Salesforce.
No parameter schema on file.
Retrieve quick actions for a specific Salesforce SObject.
No parameter schema on file.
Retrieve the PlatformAction SObject from Salesforce.
No parameter schema on file.
Retrieve information about alternate named layouts for a given Salesforce object.
No parameter schema on file.
Retrieve updated records for a specified Salesforce SObject.
No parameter schema on file.
Retrieve deleted records for a specified Salesforce SObject.
No parameter schema on file.
Describe the metadata for a specified Salesforce SObject.
No parameter schema on file.
Create a new SObject in Salesforce.
No parameter schema on file.
Retrieve compact layouts for a specific Salesforce object.
No parameter schema on file.
Retrieve a specified blob field from an individual Salesforce record.
No parameter schema on file.
Retrieve basic information about a specified Salesforce SObject.
No parameter schema on file.
Retrieve approval layouts for a specified Salesforce object.
No parameter schema on file.
Download a file from Salesforce.
No parameter schema on file.
Describe SObject layouts in Salesforce.
No parameter schema on file.
Describe SObject layouts per record type in Salesforce.
No parameter schema on file.
Lists the available objects and their metadata for your organization’s data.
No parameter schema on file.
Returns a list of layouts and descriptions for global objects.
No parameter schema on file.
Retrieve compact layouts for specified Salesforce objects.
No parameter schema on file.
Obtain an access token from Salesforce using the Web Server Flow.
No parameter schema on file.
Initiate the OAuth 2.0 Web Server Flow for Salesforce.
No parameter schema on file.
Authenticate using the Username Password Flow for Salesforce.
No parameter schema on file.
Retrieve user information from Salesforce.
No parameter schema on file.
Perform the User Agent Flow for Salesforce OAuth2 authentication.
No parameter schema on file.
Perform a SOAP login to Salesforce.
No parameter schema on file.
Retrieve Salesforce keys.
No parameter schema on file.
Revoke an access token from Salesforce.
No parameter schema on file.
Refresh the access token for Salesforce API.
No parameter schema on file.
Introspects an OpenID Connect token with Salesforce.
No parameter schema on file.
Register a new client using OpenID Connect Dynamic Client Registration Endpoint.
No parameter schema on file.
Retrieve the OpenID Connect Discovery Endpoint from Salesforce.
No parameter schema on file.
Obtain a JWT Bearer Token from Salesforce.
No parameter schema on file.
Retrieve the ID token from Salesforce.
No parameter schema on file.
Obtain an access token using Device Flow for Salesforce.
No parameter schema on file.
Initiate the device flow for Salesforce OAuth2 authentication.
No parameter schema on file.
Obtain an access token using the Client Credentials Flow.
No parameter schema on file.
Obtain an access token using the Client Credentials Flow for Salesforce.
No parameter schema on file.
Fetch the authentication configuration from Salesforce.
No parameter schema on file.
Perform an Asset Token Flow to obtain a new access token from Salesforce.
No parameter schema on file.
Refresh a sandbox in Salesforce.
No parameter schema on file.
List all sandboxes in Salesforce.
No parameter schema on file.
Retrieve a sandbox record from Salesforce.
No parameter schema on file.
Get the status of a Salesforce sandbox.
No parameter schema on file.
Delete a sandbox in Salesforce.
No parameter schema on file.
Create or clone a sandbox in Salesforce.
No parameter schema on file.
Fetch opportunities that are not closed from Salesforce.
No parameter schema on file.
Fetch early stage opportunities from Salesforce.
No parameter schema on file.
Fetch opportunities that are closing soon from Salesforce.
No parameter schema on file.
Query opportunities closing soon in Salesforce.
No parameter schema on file.
Fetch contacts from Salesforce using GraphQL.
No parameter schema on file.
Fetch contacts along with their account names from Salesforce.
No parameter schema on file.
Fetch ordered contacts from Salesforce using GraphQL.
No parameter schema on file.
Query accounts from Salesforce using GraphQL.
No parameter schema on file.
Query accounts with a filter using Salesforce GraphQL API.
No parameter schema on file.
Fetch accounts with pagination from Salesforce GraphQL API.
No parameter schema on file.
Retrieve an account by its ID from Salesforce.
No parameter schema on file.
Update an account in Salesforce.
No parameter schema on file.
Delete an account in Salesforce.
No parameter schema on file.
Create an account in Salesforce.
No parameter schema on file.
Perform an introspection query on Salesforce GraphQL API.
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Force or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.0.9. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Force can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.