Pylon
Connect Cosmo to your Pylon customer support workspace to manage issues, accounts, and contacts.
Cosmo's Pylon integration connects to Pylon's official hosted MCP server (mcp.usepylon.com). Authentication is handled directly by Pylon via OAuth 2.0 — Cosmo never stores your Pylon credentials. Tokens are kept locally on your device.
Requirements
Before connecting, ensure your user has the MCP Access role in Pylon. An org admin can assign it under Pylon → Settings → Team Members.
Connecting
- Open Cosmo Desktop → Integrations.
- Find Pylon in the "Add new integration" list and click Connect.
- Enter a label for this connection (e.g.,
Work). - A browser window opens to Pylon's OAuth login. Sign in with your Pylon account.
- After authorization, the browser redirects back to Cosmo and the connection is confirmed.
Tokens are stored locally on your device at ~/.cosmo/mcp-tokens/. They are never uploaded to the Cosmo server.
What you can do
Pylon's MCP server exposes tools for the main resources in your support workspace:
| Resource | Actions |
|---|---|
| Issues | Search, view, update issues |
| Accounts | Search, view, update accounts |
| Contacts | View contact information |
| Users | Look up team members |
The full tool list grows as Pylon updates their MCP server. Run tools/list in your MCP client to see the current set.
Connecting multiple accounts
You can connect more than one Pylon account (e.g., separate workspaces for different clients). Each connection gets its own label and isolated tokens.
Revoking access
- From Cosmo: click Disconnect next to the Pylon connector in the Integrations screen. The local token file is deleted immediately.
- From Pylon: go to Pylon → Settings → Connected Apps and revoke Cosmo's access. Existing tokens will fail on next use.
Troubleshooting
"MCP Access role required" or authorization error on connect.
Ask a Pylon admin to assign the MCP Access role to your user under Pylon → Settings → Team Members, then try again.
Pylon shows as connected but returns no data. Your Pylon session may have expired. Disconnect and reconnect to refresh tokens.
Connection times out during OAuth. The OAuth flow must complete within 2 minutes. If the browser window doesn't open, check that Cosmo is allowed to open external URLs in your OS settings.