Pylon MCP integration

Quick start

Call Pylon MCP from your generated app's worker code via the OverSkill composio client. The toolkit slug below maps to Pylon MCP's public Composio identifier — your app references it by name and OverSkill handles the OAuth round-trip.

// In your generated app's worker handler:
const composio = composioClient(env);

const result = await composio.execute(
  "PYLON_MCP_ACTION_NAME",
  { /* action parameters — see Actions section below */ }
);

return new Response(JSON.stringify(result), {
  headers: { "Content-Type": "application/json" }
});

Replace ACTION_NAME with one of the slugs listed in the Actions section below. The composio client handles auth + rate limits automatically — no API key is exposed to user code.

Setup

Setup details for Pylon MCP aren't published yet. If you need this integration in production, contact the OverSkill team and we'll prioritize it.

Available actions

12 actions exposed via the Pylon MCP integration. Each maps to a callable slug — pass it to composio.execute(...) in your worker code.

• PYLON_MCP_CREATE_ISSUE
• PYLON_MCP_GET_ACCOUNT
• PYLON_MCP_GET_CONTACT
• PYLON_MCP_GET_ISSUE
• PYLON_MCP_GET_ISSUE_MESSAGES
• PYLON_MCP_GET_ME
• PYLON_MCP_GET_USER
• PYLON_MCP_SEARCH_ACCOUNTS
• PYLON_MCP_SEARCH_ISSUES
• PYLON_MCP_UPDATE_ACCOUNT
• PYLON_MCP_UPDATE_ISSUE
• PYLON_MCP_UPLOAD_ACCOUNT_FILES