SoloFire

com.solofirePublished by solofire.comOfficial publisherv1.0.1Updated Oct 24, 2026

Med device and life science sales enablement: search content, share tracked Spaces, see engagement.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Lets an assistant search sales content, share tracked Spaces, and view engagement for med device and life science sales enablement.

What you can do
SoloFire is a remote sales enablement server for medical device and life science teams. According to the registry description, it lets an assistant search content, share tracked Spaces, and see engagement. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Consider it when an assistant needs to find sales enablement material, distribute tracked content collections to buyers or colleagues, and check how recipients engaged with them.
Requirements
A remote endpoint at developer.solofire.com over streamable HTTP. Authentication is required: either OAuth sign-in or an Authorization header carrying a SoloFire API key obtained from Admin > Developer.
Before you install
The Authorization header carries a live API key (prefix sfs_sk_live_), so treat it as a secret and prefer OAuth where possible. Sharing Spaces and viewing engagement may expose content and recipient activity data; confirm who can see shared material before using it.

Installation

In SourceWeft

  1. Open SoloFire in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.solofire%2Fspark/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "solofire": {
      "type": "http",
      "url": "https://developer.solofire.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.