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, from the content library and Spaces to engagement analytics, the built-in CRM, AI coaching, Learn, announcements and per-configuration home pages, to any AI client that speaks the Model Context Protocol, so an assistant like Claude can work with your sales content directly. For a complete factual reference of what the SoloFire platform itself does, see the platform capabilities reference.
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. Ask Spark a question and get an answer written from your approved content, with the source files it came from.
- 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 and reports. See who opened your Spaces, which files they viewed, and how long they spent, and run your account's existing reports for follow-up planning.
- Work the built-in CRM. Look up contacts, accounts and deals, log a call or meeting, create a deal, or move one to the next stage.
- Coach the team. Admins and managers author buyer personas, scenarios and sales methodologies, assign practice with due dates, and read scorecards, transcripts, the coaching overview and the skill heatmap. Reps see their own assignments.
- Run Learn. List courses and learning paths, enroll people or teams, and pull the completion report.
- Manage the library, people and teams. Create folders, upload files, change file settings, invite users and organize teams.
- Publish announcements and home pages. Post an announcement to chosen configurations, or build the home page a configuration opens to and assign it.
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, choose the scopes to grant, 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, Spaces, CRM records and coaching results your account can already see in the SoloFire apps, and nothing more. Content you don't have access to is invisible to the connection.
Most of the server only reads: 54 of the 94 tools never change anything. The other 40 do change data in your account, and each is annotated as a write operation in the server's tool definitions (create, update, or destructive), so well-behaved clients ask for your confirmation before running it. Nothing is written unless you ask for it: a connected assistant does not create a Space, upload a file, invite a user, publish an announcement, or move a deal on its own. Two more limits apply. The scopes you grant when you connect decide which groups of tools the client may use at all, and your role decides what the server offers: rep accounts get the content, Space, report, Spark, CRM, Learn and own-assignment tools, while library management, people, teams, coaching authoring and reports, announcements and home pages are hidden from rep accounts and offered to admin, manager and contributor accounts, subject to each account's permissions.
The 40 write tools, by what they do:
- Create (16):
create_space,create_folder,create_upload,invite_user,create_team,create_coaching_persona,create_coaching_scenario,create_coaching_methodology,assign_coaching_scenario,enroll_in_learning_path,create_announcement,create_landing_page,create_contact,create_account,create_deal,log_activity - Update (18):
update_folder,add_file_to_folder,remove_file_from_folder,update_file,finalize_upload,update_user,update_team,add_team_member,remove_team_member,update_coaching_persona,update_coaching_scenario,update_coaching_methodology,update_announcement,update_landing_page,set_configuration_landing_page,update_contact,update_account,update_deal - Delete or revoke (6):
revoke_space,delete_folder,delete_file,delete_team,unassign_coaching_scenario,delete_landing_page
Deleting a file, folder, team or home page and revoking a Space are marked destructive, and the server's own tool descriptions tell the assistant to confirm those with you first. Analytics already recorded for a revoked Space are kept.
Tool reference
All 94 tools in SoloFire release 1.0.32 (November 2026), grouped the way the server groups them. Access shows whether a tool reads, creates, updates, or deletes. Tools in the library management, people and teams, coaching authoring and reports, announcements, and home page groups are hidden from rep accounts.
| Tool | What it does | Access |
|---|---|---|
| Account | ||
whoami | Returns the connected company, the user the connection acts as, their role, and the scopes granted | READ |
list_configurations | Lists the configurations (workspaces) your account belongs to | READ |
| Search, reading and Spark | ||
search_content | Semantic search across the content you can access, with short excerpts | READ |
list_files | Lists files, newest first, optionally within one folder or configuration or matching a name | READ |
get_file | Returns a file's name, type, size, permissions, and timestamps | READ |
get_file_text | Returns the extracted text of an indexed file | READ |
get_download_url | Returns a short-lived signed link to download a file | READ |
ask_spark | Asks Spark a question and returns an answer written from your content, with the source files | READ |
search | Searches content and returns ids, titles and links (connector-compatible alias) | READ |
fetch | Retrieves the full text of one document by id (connector-compatible alias) | READ |
| Content library management | ||
list_libraries | Lists the content libraries this credential can reach | READ |
list_folders | Lists folders, optionally within one library or under one parent | READ |
get_folder_tree | Returns a folder and every folder beneath it | READ |
create_folder | Creates a folder at the top of a library or inside a parent | CREATE |
update_folder | Renames, describes, reorders, hides or moves a folder | UPDATE |
delete_folder | Deletes a folder and its subtree; files are unlinked, not destroyed, unless this was their only folder | DELETE |
add_file_to_folder | Links an existing file into another folder in the same library | UPDATE |
remove_file_from_folder | Unlinks a file from a folder without deleting it | UPDATE |
update_file | Renames a file or changes whether it can be shared, downloaded or seen | UPDATE |
delete_file | Deletes a file from the library and every folder and Space it is in | DELETE |
create_upload | Reserves an upload slot and returns a signed URL for the file bytes | CREATE |
finalize_upload | Registers an uploaded file once its bytes are in place | UPDATE |
| Spaces | ||
list_spaces | Lists your Spaces (every Space in scope for admins), newest first, with view counts | READ |
get_space | Returns one Space with its files and engagement | READ |
get_space_engagement | Rolls up views, viewing time, viewing days, last view and most-viewed file per Space | READ |
create_space | Creates a shareable, tracked Space from files you choose | CREATE |
revoke_space | Revokes a Space so its link stops working; recorded analytics are kept | DELETE |
| Analytics and reports | ||
list_reports | Lists the engagement reports available to run and the filters each accepts | READ |
run_report | Runs an engagement report (content views, top files, top users, Spaces, devices) for a date range | READ |
| People and teams | ||
list_users | Lists company members with role and status; managers see their scope | READ |
get_user | Returns one member's name, email, role, status and last login | READ |
invite_user | Invites someone by email with a role and optional teams | CREATE |
update_user | Changes a member's role, or deactivates or reactivates them | UPDATE |
list_teams | Lists teams with member counts | READ |
get_team | Returns one team by id | READ |
list_team_members | Lists the members of one team | READ |
create_team | Creates a team | CREATE |
update_team | Renames a team or sets its external id | UPDATE |
delete_team | Deletes a team; its members lose what was assigned through it | DELETE |
add_team_member | Adds an existing member to a team | UPDATE |
remove_team_member | Removes a member from a team | UPDATE |
| AI coaching | ||
list_coaching_personas | Lists the buyer personas the AI plays in roleplay practice | READ |
get_coaching_persona | Returns one persona with its description, reference content and configurations | READ |
create_coaching_persona | Creates a buyer persona, optionally restricted to chosen reference content | CREATE |
update_coaching_persona | Edits a persona's role, description, reference content or configurations | UPDATE |
list_coaching_scenarios | Lists the assignable roleplay scenarios | READ |
get_coaching_scenario | Returns one scenario in full: persona, situation, documents, grading criteria, reminders | READ |
create_coaching_scenario | Creates an assignable roleplay scenario | CREATE |
update_coaching_scenario | Edits a scenario | UPDATE |
list_my_coaching_scenarios | Lists the scenarios assigned to the connected user, with due dates and best scores | READ |
list_coaching_assignments | Shows who a scenario is assigned to, with status, attempts and scores | READ |
assign_coaching_scenario | Assigns a scenario to users or teams with an optional due date | CREATE |
unassign_coaching_scenario | Removes a scenario assignment; completed sessions are kept | DELETE |
list_coaching_sessions | Lists roleplay sessions with scores, win condition and flagged claims | READ |
get_coaching_session | Returns one session's scorecard, claim checks, live flags and transcript | READ |
get_coaching_overview | Summarizes coaching results over a window: sessions, scores, win rate, completion, leaderboard | READ |
get_coaching_heatmap | Returns per-user average scores on each methodology dimension | READ |
list_coaching_methodologies | Lists the sales methodologies sessions can be scored against | READ |
get_coaching_methodology | Returns one methodology with its weighted dimensions | READ |
create_coaching_methodology | Creates a company sales methodology with 1 to 12 weighted dimensions | CREATE |
update_coaching_methodology | Edits a company methodology (the built-in library is read-only) | UPDATE |
| Learn | ||
list_courses | Lists courses and the configurations they are assigned to | READ |
get_course | Returns one course with its lesson outline and learning paths | READ |
list_learning_paths | Lists learning paths with enrollment counts | READ |
get_learning_path | Returns one path with its ordered courses and unlock offsets | READ |
list_enrollments | Lists enrollments with per-course progress | READ |
enroll_in_learning_path | Enrolls users or teams in a learning path from a start date | CREATE |
get_learn_report | Returns course completion over a window, by course or by user | READ |
| Announcements | ||
list_announcements | Lists announcements with text, audience, files and read counts | READ |
get_announcement | Returns one announcement in full | READ |
create_announcement | Publishes an announcement to chosen configurations, with push and email notification unless turned off | CREATE |
update_announcement | Edits an announcement's title, text, audience or files | UPDATE |
| Home pages (landing pages) | ||
list_landing_pages | Lists the company's built landing pages and the configurations using each | READ |
get_landing_page | Returns one landing page with its full block document | READ |
create_landing_page | Creates a built landing page from a block document; shown once a configuration selects it | CREATE |
update_landing_page | Renames a landing page or replaces its blocks; every configuration using it updates on next sync | UPDATE |
delete_landing_page | Deletes a landing page; configurations using it lose their home page until another is chosen | DELETE |
get_configuration_landing_page | Shows what a configuration opens to: none, a ZIP package, or a built page | READ |
set_configuration_landing_page | Sets a configuration's home page to a built page, a ZIP package (optionally full screen on launch), or none | UPDATE |
| CRM | ||
list_contacts | Lists the CRM contacts you can see, with filters | READ |
get_contact | Returns one contact in full | READ |
create_contact | Creates a contact, optionally linked to an account | CREATE |
update_contact | Edits a contact | UPDATE |
list_accounts | Lists CRM accounts | READ |
get_account | Returns one account in full | READ |
create_account | Creates an account | CREATE |
update_account | Edits an account | UPDATE |
list_pipelines | Lists deal pipelines and their ordered stages | READ |
list_deals | Lists deals with amount, stage, status, close date, account and contacts | READ |
get_deal | Returns one deal in full | READ |
create_deal | Creates a deal in a pipeline stage | CREATE |
update_deal | Edits a deal, moves it to another stage, or closes it with a reason | UPDATE |
list_activities | Lists the activity timeline for a contact, account or deal | READ |
log_activity | Logs a note, call, email, meeting or SMS against a contact, account or deal | CREATE |
The server also publishes four prompts: meeting_prep, follow_up_digest, account_brief, and design_coaching_scenario. Each is a ready-made request your client can offer that chains the tools above.
Home page SDK (window.SoloFire)
Every configuration can open to its own home page. A page built in the admin page builder needs no code. An HTML package (a ZIP in the content library) is for teams that want a page their agency built: the app injects a window.SoloFire bridge into it on web, iOS, Android, macOS and Windows, so the package never bundles the SDK. Every call is limited to content the signed-in user can already see in that configuration.
- Lifecycle: a
readypromise that resolves when the bridge is available, and acontextobject carrying the signed-in user, company, configuration and theme colors. - Methods:
getFolders,getFiles,getTree,openFile,openFolder,share,navigate,openUrlandexitFullscreen. - Events: connectivity changes and presentation changes (for example entering or leaving full screen), so a page can adapt when a rep goes offline.
- REST API: a
landing_pagesresource (list, get, create, update, delete) and/v1/configurations/{id}/landing_pageon the configurations scopes. - MCP tools:
list_landing_pages,get_landing_page,create_landing_page,update_landing_page,delete_landing_page,get_configuration_landing_pageandset_configuration_landing_page, listed in the tool reference above.
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, work your CRM and coaching, 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, Spaces, CRM records and coaching results 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?
Only when you ask it to. Reading never changes anything, and 54 of the 94 tools are read-only. The other 40, such as creating a Space, uploading a file, moving a deal, publishing an announcement or assigning coaching, are annotated as write operations so your AI client confirms each one with you first, and the scopes you grant when you connect limit what a client may touch at all. 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.