Use Cursor from Claude
Add the Cursor connection to a Space that runs Claude, then use it from every channel in that Space.
Connect Cursor once, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.
Add the Cursor connection to a Space that runs Claude, then use it from every channel in that Space.
Add the Cursor connection to a Space that runs Codex, then use it from every channel in that Space.
Connect your own OpenClaw to Sidekick while Type.com provides the conversations, permissions, connections, skills, and automations.
Cursor is an AI-powered code editor built on VSCode. The API provides access to Cloud Agents, Admin, Analytics, and AI Code Tracking features.
Connect Cursor once, then decide which Spaces can use it in threads, skills, automations, and coding work.
Once Cursor is connected in Type.com, install the Type.com CLI, and Claude Code or Codex can call its tools with type-cli integrations call. Calls run with your Type.com access, and the credentials stay on Type.com's servers.
In a Space with Cursor connected, describe the job, and Type.com proposes an automation with its trigger, schedule, and destination. Runs can start on a schedule or from a webhook, Slack, GitHub, Linear, email, or RSS, and each run leaves a thread the team can read.
Tool to retrieve the conversation history for a specific cloud agent. Use when you need to view the messages exchanged between the user and the agent. Returns error with status 404 if the agent is not found or access is denied.
Tool to retrieve API key information including the key name, creation date, and owner email. Use when you need to verify API key details or validate authentication.
Tool to retrieve a paginated list of all Cursor Cloud agents. Use when you need to view existing agents, their status, or iterate through agents with pagination.
Tool to retrieve the list of available AI models in Cursor. Use when you need to discover which models are available for API requests.
Tool to list GitHub repositories accessible to the authenticated user. Use when you need to retrieve all repositories the user has access to through their Cursor account.
Cursor is an AI-powered code editor with codebase-aware chat, agentic editing, rules, model configuration, terminal/CLI workflows, and bring-your-own model API key settings. Public docs focus on product and editor capabilities rather than a broad public REST API, so connected workflows should center on documented Cursor settings and CLI/editor automation surfaces.
Yes. Connect Cursor to a Space that runs Claude, then use its approved tools and data from any channel in that Space.
Yes. Connect Cursor to a Space that runs Codex, then use its approved tools and data from any channel in that Space.
Yes. Once Cursor is connected in Type.com, install the Type.com CLI, and Claude Code or Codex can call its tools with type-cli integrations call. Calls run with your Type.com access, and the credentials stay on Type.com's servers.
Yes. In a Space with Cursor connected, describe the job, and Type.com proposes an automation with its trigger, schedule, and destination. Runs can start on a schedule or from a webhook, Slack, GitHub, Linear, email, or RSS, and each run leaves a thread the team can read.
Not exactly. Type.com uses connectors and connections to give selected Spaces access to approved app tools and data. Some connectors use hosted MCP, while others use OAuth, API keys, service accounts, or custom APIs.
Connect Mapulus to Claude in Type.com to find locations, review maps, and check map details in a shared thread.
Connect Marketstack to Claude in Type.com to pull stock prices, dividends, and exchange data in a shared thread.
Connect Matterport to Claude in Type.com to search models, pull model details, and check webhook configurations from a shared thread.
Connect Mercury MCP to Claude in Type.com to check account balances, review transactions, and pull statements without touching the Mercury dashboard.