Connect Muse.

Keep a record of emails sent, meetings changed, and purchases made by Muse.

For Muse. Paste into your agent to begin.

Paste into Muse
Your agent will handle the setup steps it supports.
Approve the connection
Choose your Monologue feed when sign-in opens. You approve reading and reporting in that feed.
Confirm it’s ready
Ask your agent to check its connection and reporting instructions. It may need one restart.

Muse’s available connection tools can vary. The instructions ask it to use a supported connection and explain any step you need to complete.

Review the instructions

Set up Monologue for Muse. Use my Monologue instance at https://www.monologue.events.

Read and execute https://www.monologue.events/agent-setup.

Use https://www.monologue.events as MONOLOGUE_URL for this setup, including approval links and manual-key fallback. This instance replaces the guide's hosted defaults; do not switch to another service if setup fails.

Ask me to choose the workspace during connection approval. Keep the connection bound to that workspace.

If your client supports secure MCP setup, use https://www.monologue.events/mcp; otherwise use this instance's approval-link flow.

Request actions:read and actions:write together in one connection approval. Read and add reports with the same feed access I have in the chosen workspace; access follows my current membership. Reuse an existing connection only for this instance and workspace. Preserve any existing URL/credential pairing. An older limited connection needs reconnection and approval before gaining access; never silently broaden it. Never display credentials. This prompt grants no access by itself.

Install the canonical monologue skill using your supported skill manager so the reporting instructions persist in later sessions. Do not duplicate the skill into several rule files.

Before adding anything, check for a working connection and discoverable skill. Reuse them. Preserve an explicitly configured MONOLOGUE_URL/MONOLOGUE_API_KEY pairing and never switch it to another instance. Do not overwrite unrelated client settings or expose configuration secrets.

If your client supports persistent skills or instructions, use its native mechanism. If instructions apply only to this conversation, tell me clearly.

Use this agent's documented native connection settings. If it cannot configure itself, give me one exact next step. The MCP endpoint is https://www.monologue.events/mcp.

Follow the shared permission policy above: the standard connection requests reading and reporting together in one approval. Older limited grants must not gain access silently. Start authentication when supported, then let me sign in and approve the intended feed; never hard-code a demo or test workspace or approve on my behalf.

Confirm the skill is discoverable and the actual reporting tool is available in the execution context. If a restart is required, give one clear restart/resume step and verify afterward. For API-only setup, distinguish configured credentials from a successful report. Do not invent a test action or write a synthetic event to my feed.

Finish with a short setup result: instructions available, connection status, granted permissions and any remaining step. After my next authorized external action, report its actual outcome and return the real event ID. Research, drafts, local development and Monologue tool calls stay out.

Keep using your agent

Already connected? Reuse that connection and confirm the reporting instructions are available. You approve reading and reporting in the workspace you choose.

After the next real action, check your feed. Ask your agent for the returned event ID if a report is missing.

Example

Sent the counteroffer to the dealer.

Research, drafts, and local development stay out of the feed. Reports can be incomplete or mistaken; Monologue is a record, not independent verification.

Need a useful first task? Pick a starter prompt. Building your own connector? See the API.