Set up Claude or Codex
Use the workspace URL and an account-consent flow, not shared API keys.
Start in outwrite.ai's AI connections section and copy the server URL. The exact URL comes from the environment you are signed into.
Claude on the web
In Claude's connector settings, add a custom remote connector. Enter a recognizable name such as outwrite.ai and paste the MCP server URL.
Follow the connection's authorization prompt. Sign into outwrite.ai, choose the workspace and review the requested permissions. Return to Claude and enable the connector in the conversation where you want to use it.
Availability and labels depend on your Claude plan and current interface. If custom connectors are not available, use another client that supports remote MCP with OAuth.
Codex
For a CLI setup, replace the example URL below with the exact one copied from your workspace:
codex mcp add outwrite --url "YOUR_WORKSPACE_MCP_SERVER_URL"
codex mcp login outwrite
Complete the browser consent flow. A new Codex session may be needed to load a newly added connection. In the desktop app, the corresponding MCP settings can also manage configured servers.
Test with a read-only request
Ask: “List my authorized outwrite.ai workspaces, then summarize the selected workspace's plan.”
The assistant should call the workspace and overview tools. A connection that appears in settings but cannot read the workspace is not yet verified.
Choose the right permissions
Use read access for reporting. Add management permissions only if you want the assistant to change something. Publishing permission is separate.
You can revoke an existing connection in outwrite.ai and reconnect with different permissions. Do not share browser callback codes, access tokens or credentials with other people.
Troubleshooting
If consent expires, start a fresh connection flow. If a tool is missing, check the granted scopes. If the client cannot reach the server, confirm it supports remote HTTP MCP and the URL is from the correct environment.
For an account with expired platform access, resolve billing through the product. The MCP connection does not bypass account access checks.
