Skip to main content
Muse Code is Meta’s terminal coding agent. You can connect it to TryPost’s MCP server and manage scheduling in natural language — this is the path we verified. The personal agent (the character on muse.ai) is Muse AI Agent.

​
Prerequisites

  • Muse Code installed:
  • A TryPost Cloud account with an active trial or subscription (start a 7-day free trial)

​
Setup

1

Start Muse Code

2

Ask it to add the TryPost MCP server

Paste the URL and let Muse write the config. For example:
Muse names the server trypost and tells you to authorize it with:
3

Authorize in the browser

Run that command in your terminal (outside the Muse session if it printed it as a next step). Muse opens a browser to TryPost. Sign in, review the permissions, and click Allow.The login argument must match the server key in settings — trypost if that’s the name Muse chose.
4

Use TryPost in Muse Code

Back in the session, ask:
TryPost MCP accepts OAuth with the mcp:use scope. Personal Access Tokens from Settings → API Keys are rejected (403). After muse mcp login trypost, Muse stores and refreshes the grant. To disconnect: muse mcp logout trypost.
MCP tools in Muse Code are not sandboxed. They run as a direct network connection, outside the filesystem sandbox. Approval still applies.

​
Manual configuration

If you prefer to edit the file yourself, put this in ~/.config/muse/settings.json. The file must include "schema_version": 1. Muse Code 1.1 writes the block under mcpServers (not mcp_servers):
Merge into an existing file. Do not add a second mcp_servers block alongside mcpServers — that faults the config and muse mcp login refuses to run. Then:
No Authorization header. OAuth is discovered from the URL.

​
Example prompts

Using the personal agent instead of the terminal? See Muse AI Agent.