What the SoloFire MCP server does
SoloFire is a sales enablement platform for medical device and life science field sales teams. Companies organize sales content — PDFs, presentations, videos, sales training material — into libraries their field teams use in the SoloFire apps, and reps share files with customers as tracked Spaces (digital sales rooms) that report who viewed what and for how long. The SoloFire MCP server exposes that same account — the content library, Spaces, and engagement analytics — to any AI client that speaks the Model Context Protocol, so an assistant like Claude can work with your sales content directly.
What you can do with it
- Search and read your content library. Find the right file by topic, read its text, or get a download link — without opening the app.
- Build and share tracked Spaces. Ask your assistant to assemble the right files into a shareable Space for a specific customer, then revoke it when the deal closes.
- Pull engagement analytics. See who opened your Spaces, which files they viewed, and how long they spent — useful for prioritizing follow-up.
- Run reports. Execute your account's existing reports and use the results in analysis, summaries, or follow-up planning.
Connect it
The server is a remote MCP server (streamable HTTP transport). There is nothing to install — you point your client at one URL:
https://developer.solofire.com/mcpRequirements: an active SoloFire account. MCP access is included for every user on every account — there is no separate plan, add-on, or admin approval required. Not a SoloFire customer yet? See pricing.
Claude (web and desktop)
- Open Settings → Connectors in Claude (claude.ai or the Claude desktop app).
- Choose Add custom connector.
- Name it SoloFire and paste the URL:
https://developer.solofire.com/mcp - Click Add, then Connect. A SoloFire login window opens — sign in with your normal SoloFire credentials and approve access.
- Start a new chat and try: “Search my SoloFire library for our latest product brochure.”
Claude Code
claude mcp add --transport http solofire https://developer.solofire.com/mcpThen run /mcp inside Claude Code to authenticate.
Other MCP clients
Any MCP-compatible client that supports remote servers over streamable HTTP works with the same URL, including ChatGPT (developer mode connectors). The server is listed in the official MCP Registry as com.solofire/spark.
Authentication and permissions
Authentication uses OAuth: when you connect, you sign in to SoloFire and grant access, and the client receives a token scoped to your account. SoloFire never shares your password with the AI client. For programmatic or server-to-server use, API keys are also supported as bearer tokens — see the SoloFire developer documentation.
Access follows your existing SoloFire permissions. A connected client sees only the configurations, libraries, folders, files, and Spaces your account can already see in the SoloFire apps — nothing more. Content you don't have access to is invisible to the connection.
Almost every tool is read-only. Exactly two tools change anything:
create_space— creates a new shareable Space from files you chooserevoke_space— disables an existing Space's share link
Both are annotated as write operations in the server's tool definitions, so well-behaved clients ask for your confirmation before running them. Everything else — search, reading files, listing Spaces, engagement analytics, reports — is read-only.
Tool reference
| Tool | What it does | Access |
|---|---|---|
| Account | ||
whoami | Returns the authenticated user, account, and permissions in play | READ |
list_configurations | Lists the configurations (workspaces) your account belongs to | READ |
| Content library | ||
list_libraries | Lists content libraries in a configuration | READ |
list_folders | Lists folders in a library | READ |
get_folder_tree | Returns the full folder hierarchy of a library | READ |
list_files | Lists files in a folder or library | READ |
get_file | Returns a file's metadata | READ |
get_file_text | Extracts the text content of a file | READ |
get_download_url | Returns a time-limited download link for a file | READ |
| Search | ||
search | Searches files and Spaces by name and metadata | READ |
search_content | Searches inside file content for material about a topic | READ |
fetch | Retrieves a single item by ID from search results | READ |
| Spaces | ||
list_spaces | Lists your shared Spaces | READ |
get_space | Returns a Space's details and contents | READ |
create_space | Creates a shareable, tracked Space from selected files | WRITE |
revoke_space | Disables a Space's share link | WRITE |
| Analytics & reports | ||
get_space_engagement | Shows who viewed a Space, which files, and for how long | READ |
list_reports | Lists the reports available to your account | READ |
run_report | Runs a report and returns the results | READ |
Data handling and privacy
The MCP server is part of SoloFire's SaaS platform and handles your data under the same terms as the SoloFire apps: content and analytics stay in your SoloFire account, and responses are returned directly to the AI client you connected. SoloFire does not use your content to train AI models. What an AI client does with retrieved data is governed by that client's own terms. See the SoloFire privacy policy for full details.
Support
Questions or problems connecting? Email info@solofire.com and mention “MCP” in the subject line — the request routes straight to the team that runs the server. Help articles and tutorials live in the support center.
FAQ
What is MCP and why would I connect SoloFire to it?
The Model Context Protocol (MCP) is an open standard that lets AI assistants like Claude connect to outside tools and data. Connecting SoloFire means your assistant can search your sales content library, build tracked Spaces, and answer questions from your engagement analytics instead of guessing.
Do I need an admin account?
No. Any active SoloFire user can connect. The connection uses your own SoloFire login and inherits your existing permissions.
Can it see content I don't have access to?
No. The MCP server enforces the same permissions as the SoloFire apps. A connected AI client sees only the configurations, libraries, files, and Spaces your account can already see.
Does it work with anything other than Claude?
Yes. Any MCP-compatible client that supports streamable HTTP remote servers can connect with the same URL, including ChatGPT with developer mode connectors, Claude Code, and other MCP clients.
Does connecting it change anything about my SoloFire account?
No. Connecting is read-only by default. The only two actions that change anything are creating a Space and revoking a Space, and both only happen when you ask for them. You can disconnect at any time from your AI client's settings.
Is there a cost?
No. MCP access is included with every SoloFire account. SoloFire has one plan with everything included, so there is no add-on or upgrade required.