Spark

io.github.PlusDocsPublished by GitHub account PlusDocsv1.0.2Updated Oct 30, 2026

Build and run a business from your AI assistant, with hosting, payments, email and more built in.

Overview

AI-generated overview

Spark's remote MCP server lets an assistant plan, build, preview and publish small business sites and apps with hosting, payments, email and marketing built in.

What you can do
  • Plan and create projects: plan a new project one question at a time, then create it and start the first build
  • Inspect projects: list projects with addresses and unpublished changes, read one project's pages, internal tools, setup progress and pending questions, and review recent publishes and requests
  • Send requests and follow them: send a request about a project, a page or an internal tool with up to five files, follow the turn, answer Spark's questions or approvals, and stop a build
  • Check and publish: view a preview screen at desktop or phone width, then publish the newest version
  • Account and plan: see which account is signed in, its organizations, and remaining build credits
When to use it
Useful when you want an assistant to help you stand up and iterate on a small business site or app — booking pages, customer accounts, Stripe payments, customer email and marketing — without leaving the chat, and to check and publish the result.
Requirements
A remote server at mcp.spark.site using streamable HTTP with OAuth sign-in; no API key. A Spark account on any plan is needed, and payments or a custom domain require a paid plan. Building consumes the plan's build credits.
Before you install
Tools act as the signed-in Spark account within its organizations, so the assistant can create projects, send requests, answer approvals and publish live sites. Publishing and changes may be confirmed per request by the client. Builds spend plan credits, and payments run through Stripe on a paid plan. Requests can include uploaded files, and messages appear in the project's chat in Spark.

Installation

In SourceWeft

  1. Open Spark 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/io.github.PlusDocs%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": {
    "spark": {
      "type": "http",
      "url": "https://mcp.spark.site/"
    }
  }
}

README

Spark MCP

Build and run a business from your AI assistant with Spark: sites and apps with hosting, customer accounts, payments, email and marketing built into the platform. This is the official plugin for Spark's remote MCP server, for ChatGPT, Claude, Claude Code, Cursor, Codex and any other MCP client.

You:    Plan a new Spark project with me: a booking site for my pottery classes that takes payments.Agent:  Spark has a plan for Clay Studio Bookings. Shall I create it?You:    Yes.Agent:  Spark is building it. Your preview: https://app.spark.site/projects/…

What Spark is

Spark is a platform for building and running a business. You describe what you want, and Spark designs it, writes the code and publishes it. A project is the whole business, and what it needs to run is built into the platform:

  • Hosting on a spark.site address or your own domain.
  • Customer accounts: sign-in for your customers, and what each one has bought.
  • Payments through Stripe: one-off sales and subscriptions, paid out to you.
  • Email to your customers.
  • Marketing: a marketing plan for the business and the content to go with it.
  • Internal tools for running it, such as customer and payments dashboards, which Spark builds and changes like the site.

Through this server, your assistant works in a project's chat the way you would in Spark. It sends your requests, follows Spark while it works, brings Spark's questions and approvals back to you, looks at the preview and publishes.

What to expect.

  • A change usually takes a few minutes, and a new project's first build about ten. The assistant waits for Spark and reports what it is doing meanwhile.
  • Spark asks before some actions, such as deleting data. Your assistant shows you the question, and nothing happens until you answer.
  • Messages your assistant sends appear in the project's chat in Spark, marked as sent from that assistant, so you can carry on in either place.
  • Building uses the Build credits of your Spark plan, as it does in Spark.

Requirements

A Spark account, on any plan. The Free plan includes one-time credits for building, and you can publish on a spark.site address. Taking payments and using your own domain need a paid plan. See pricing.

You don't need an API key: you sign in with your Spark account the first time you use the server.

Install

ChatGPT. Open Plugins, select +, then Add custom MCP server. Name it Spark, enter https://mcp.spark.site as the server URL with OAuth authentication, and create it. In a chat, type @ and pick Spark. See OpenAI's guide.

Claude (claude.ai, desktop and mobile). Go to Customize → Connectors, select + Add, then Add custom connector. Name it Spark, enter https://mcp.spark.site, and select Continue, then Add. In a chat, turn it on under + → Connectors. On Team and Enterprise plans, an Owner adds it under Organization settings → Connectors and each member selects Connect. See Spark's guide.

Claude Code. Install the plugin, which adds the MCP server and the build-with-spark skill:

/plugin marketplace add PlusDocs/spark-site-mcp/plugin install spark@spark

Then ask for a change, or run /spark:build-with-spark add a pricing page to my Harbor Tours site. To add only the MCP server: claude mcp add --transport http spark https://mcp.spark.site

Codex. Add this repository as a plugin marketplace, then install Spark.

Cursor and any other MCP client. Add the server to the client's MCP config:

json
{  "mcpServers": {    "spark": {      "type": "streamable-http",      "url": "https://mcp.spark.site"    }  }}

On first use, the client opens Spark's sign-in. Sign in to Spark if you aren't already, then choose Connect.

Tools

ToolWhat it does
whoamiSays which Spark account the server is signed in as, and its organizations.
list_projectsLists your projects with their addresses and whether they have unpublished changes.
get_projectOne project: its site's pages, its internal tools, what Spark is doing and any question it is waiting on, and the setup plan's progress.
plan_projectPlans a new project with you, one question at a time, ending with a plan to agree to. Creates nothing.
create_projectCreates the project you agreed to and starts its first build.
send_messageSends a request to Spark on a project, optionally about one page or internal tool, with up to five files.
get_turnFollows a request: what Spark is doing, its reply when done, and the questions it is waiting on. Waits up to 50 seconds per call.
answer_questionAnswers Spark's question or approval, with the choice you picked.
stop_buildStops Spark's work on a request. The changes made so far stay in the preview.
view_pageShows one screen of a page of the preview, at desktop or phone width, so the assistant can check the work.
attach_filesShows Spark's upload card, where you pick files from your computer to send with your next request.
get_historyWhat happened on a project lately: its publishes and recent requests.
get_creditsYour plan and the credits you have left.
publish_projectPublishes the newest version of a project's site once Spark has finished.

In clients that support MCP Apps, such as Claude and ChatGPT, a project shows as a card. The card follows Spark while it works, shows its questions with their choices, and has Publish, Stop and Open in Spark. In Claude, after a change, it shows a picture of the part of the site that changed. Other clients get the same results as text.

Example prompts

  • "Plan a new Spark project with me: a booking site for my pottery classes that takes payments."
  • "What is Spark working on in my Harbor Tours project?"
  • "Ask Spark to add a pricing page with our three class packages, then check it on a phone."
  • "Ask Spark to email my customers about the new spring classes."
  • "Send Spark this menu and ask it to put it on the home page: https://example.com/menu.pdf"
  • "Publish Harbor Tours."

Notes

  • Tools run as the Spark account that signed in, in that account's organizations.
  • Clients may ask you to confirm each request that changes a project, and each publish.
  • To disconnect an assistant, open Account settings in Spark and go to Connected assistants.
  • Spark hosts the server. This plugin runs no local code.

Links

What's in this repository
PathPurpose
.mcp.jsonMCP server config used by Claude Code, Cursor and Codex
plugin.json, mcp.jsonPortable Agent Plugins manifest and MCP config
.claude-plugin/Claude Code plugin manifest and marketplace entry
.cursor-plugin/Cursor plugin manifest
.codex-plugin/, .agents/plugins/Codex plugin manifest and marketplace entry
skills/build-with-spark/Skill with guidance on using the tools well
assets/Logo

The server's listing in the official MCP Registry is io.github.PlusDocs/spark, published with the server itself.

License

MIT

Source: README.md at commit 2b655b2

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

2
  1. v1.0.2LatestOct 29, 2026
  2. v1.0.0Oct 23, 2026

Score

85% 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
  • License10 pts