Lets an assistant commission a multi-model AI spec committee and receive rubric-scored, build-ready specifications.
What you can do
The server exposes a single tool, sparkvibe.get_started, which works without a credential. It returns the preferred OAuth 2.1 connection flow, the Pro plan price and build-credit allowance, the agent-initiated checkout flow, the manual-key fallback, and a ready-to-relay message for the user. The registry description says the service commissions a multi-model AI spec committee that produces rubric-scored, build-ready specs.
When to use it
Use it when you want an assistant to turn a request into a scored, build-ready specification through a multi-model committee. The get_started tool is also meant to be called when another tool returns UNAUTHORIZED or FEATURE_LOCKED, or when connection details are needed.
Requirements
A remote streamable HTTP endpoint at api.sparkvibeai.com. Authentication is via an Authorization header: preferably OAuth 2.1 sign-in with RFC 9728/8414 discovery, or alternatively an agent API key in the svai. . format. The get_started tool works without a credential.
Before you install
The Authorization header carries a bearer token or agent API key, so treat it as a secret. The service involves a paid Pro plan and build credits, and the get_started tool describes an agent-initiated checkout flow, so spending may be triggered. Review the plan and credit terms before connecting.
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.sparkvibeai%2Fspec-committee/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.
Works WITHOUT a credential. Returns the preferred OAuth 2.1 connection flow, the Pro plan price and build-credit allowance, the agent-initiated checkout flow, the manual-key fallback, and a ready-to-relay message for your user. Call this when another tool returned UNAUTHORIZED / FEATURE_LOCKED or you need setup instructions.
Takes no parameters.
Version history
1
v1.1.0LatestSep 16, 2026
Score
83%
83% 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 listedRequired15 pts
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.