Solace MCP Server
8 tools via Model Context Protocol — JSON-RPC 2.0 over stdio. Every call is OAuth3-scoped and SHA-256 evidenced.
8 MCP Tools
Every tool is OAuth3-scoped, meaning your agent requests only the permissions it needs. All actions produce tamper-evident SHA-256 evidence automatically.
detect_apps
Detect which Solace apps are available for a given URL so the Hub can recommend the right workflow automatically.
scope: readlist_apps
List all apps currently loaded in Solace Hub so an agent can reason over the installed local capability surface.
scope: readcreate_schedule
Create a cron-backed Hub schedule for an app or URL. This is the entry point for recurring autonomous runs.
scope: automatelist_schedules
Inspect every active schedule currently owned by the Hub.
scope: readdelete_schedule
Delete a schedule by UUID when an agent or user no longer wants the job to recur.
scope: automaterecord_evidence
Write a structured event into the append-only evidence log. ALCOA+ compliant and FDA Part 11 ready.
scope: evidencelist_evidence
Read back evidence records with pagination for audits, reviews, and human sign-off flows.
scope: evidenceget_hub_status
Read the Hub runtime health, readiness, and current service status.
scope: readConnect in 3 Steps
Get an API key
Sign up at solaceagi.com and create a scoped API key with the automate scope.
Add to your Claude settings
Add the MCP server configuration to .claude/settings.json:
Use natively in Claude Code
Claude Code will now call the 8 Hub-native tools directly, including detect_apps, create_schedule, and get_hub_status.
JSON-RPC 2.0 Examples
detect_apps
create_schedule
record_evidence
get_hub_status
Machine-Readable Manifest
Fetch the full JSON manifest for automated discovery: