Connect Artie to Claude
Connect your Artie workspace and use your hired Artisans in Claude.
Claude uses Artie’s remote MCP server. The host connection, Artie workspace grant and any connected third-party accounts are separate setup steps. Public directory availability is separate from a custom connection.
On this page
Before you connect
Use a Claude account and plan that supports remote MCP/custom apps. Your host or organization may require an admin to allow the connection. You also need an active Artie workspace member and a hired Artisan.
Add the Artie server
Open Claude app/connector settings and add a custom remote MCP connection named Artie. Use https://api.artie.ai/api/mcp for production. Choose OAuth when the host asks about authentication. Exact labels and plan availability can change; follow your host’s current custom-connector instructions.
Sign in and choose the workspace
Complete the Artie sign-in flow with the intended account. Review OAuth access, then review the separate Artie workspace connection. Confirm the workspace name before connecting. This connection acts within that member’s existing authority; it does not connect every company app or grant access to coworkers’ private records.
Try a useful request
Start a new conversation with Artie selected. Ask: “Which Artisans can I work with? Ask my Generalist to draft a board update using only these fictional figures: cash $2.4m, net burn $180k per month, MRR $96k versus $80k last month. Include formulas and assumptions; keep it private and do not send anything.” Read progress and the completed result separately.
Maintain or disconnect the connection
If the host caches tool definitions, use its supported tool refresh after a schema update. For auth expiry, restore the same intended account connection. Review connections in Artie Account settings to disconnect access. Disconnecting the external client is separate from cancelling already accepted tasks; cancel unwanted work explicitly.
Need help with your workspace?
Contact support