Go beyond a general web answer
Turn live social signals into a focused market brief.
What to ask forA sourced brief with buying concerns and content ideas.
Give Muse fresh research, SEO and social data for the work you hand it. Keep the conversation in Muse, with SpringBrand tools behind the answers.
Install or update SpringBrand in Muse using https://plugin.springbrand.ai/INSTALL.md. Follow the Other Agent workflow and verify that Muse can access SpringBrand tools.Choose a task, copy the request and try it in your connected agent. The outputs below describe what to ask for.
Turn live social signals into a focused market brief.
What to ask forA sourced brief with buying concerns and content ideas.
Use SEO data to decide what is worth writing.
What to ask forFive keyword opportunities with intent and supporting data.
Find relevant creators and compare their recent work.
What to ask forA creator shortlist with links and reasons to review each profile.
Copy the setup prompt into Muse. The production guide uses @springbrand/cli@latest and the Other Agent workflow with the generic client. Muse needs an execution environment that allows the installation.
Install or update SpringBrand in Muse using https://plugin.springbrand.ai/INSTALL.md. Follow the Other Agent workflow and verify that Muse can access SpringBrand tools.Follow the guide’s next action to connect springbrand to https://connector.springbrand.ai/mcp in the environment Muse uses. Complete the supported OAuth flow or provide your production API key through the requested authentication step. CLI installation alone is not a completed host connection.
Follow the connection report’s verification step. Confirm that Muse can retrieve SpringBrand tools from the authenticated server. If its environment cannot install the CLI, follow the guide’s direct remote MCP recovery path where supported.
The SpringBrand MCP server follows a discover-then-run pattern. Your agent searches the catalog for an operation that matches the task, reads its input contract, then runs it and reads the result.
Discovery and schema lookups never execute anything, so your agent can explore safely before it commits to a run. Some operations ask you to connect a third-party account the first time; the agent tells you which one is missing.
| Tool | What it does |
|---|---|
| search_tools | Find operations that match a task description |
| get_tool_schemas | Read the input and output contract of an operation |
| execute_tools | Run one or more operations |
| get_execution | Read the status and saved result of a run |
| manage_connections | List the third-party accounts an operation needs and check their status |
No. It gives you a setup request and example tasks. You complete the connection and authorization in the flow supported by your Muse account.
Use INSTALL.md and its Other Agent workflow for Muse. The generic client prepares a connection but cannot configure every host automatically; follow the returned next action and verify access from Muse. A CLI success message alone does not confirm that Muse can use the tools.
SpringBrand tool usage draws from your SpringBrand Credits balance. Your host agent’s subscription and usage are billed separately. Check the operation and current price before running a paid task.
No. These are example task requests and expected deliverables. Copy one into your connected agent to run it; no tool call or charge happens when you copy it.
Connect your SpringBrand account, choose a small task and review the result.