Can I use Devin as a CLI?

Yes. KosmoKrator exposes a Devin CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Devin through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Devin tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Devin credentials stored?

Devin credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Devin MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

Devin MCP Integration for Vercel AI SDK

Connect Devin to Vercel AI SDK through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

5 functions 3 read 2 write API key auth

Submit Devin feedback View package source

Connect Devin to Vercel AI SDK

Use KosmoKrator as a local integration gateway for Vercel AI SDK agents and scripts.

Create an MCP client that starts or connects to the KosmoKrator gateway for the selected integration. The gateway is local, scoped to this integration, and starts with --write=deny so Vercel AI SDK can inspect read-capable tools without receiving write access by default.

Devin MCP Config for Vercel AI SDK

Prefer CLI JSON calls when a workflow only needs one deterministic integration operation.

{
  "mcpServers": {
    "kosmokrator-devin": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=devin",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=devin --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Devin instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Devin Tools Visible to Vercel AI SDK

Vercel AI SDK sees stable MCP tool names generated from the Devin integration catalog.

MCP tool	Source function	Type	Description
`integration__devin__devin_create_session`	`devin.devin_create_session`	Write	Create a new Devin AI session. Provide a task prompt describing what you want Devin to do. Optionally provide an idempotency key to prevent duplicate sessions.
`integration__devin__devin_get_session`	`devin.devin_get_session`	Read	Retrieve details and current status of a Devin session. Use this to check progress on a task, view the session state, or get the output.
`integration__devin__devin_list_sessions`	`devin.devin_list_sessions`	Read	List all Devin sessions. Returns an overview of all sessions including their IDs, statuses, and creation times.
`integration__devin__devin_send_message`	`devin.devin_send_message`	Write	Send a message to an existing Devin session. Use this to provide additional instructions, ask questions, or guide the AI during an active session.
`integration__devin__devin_get_current_user`	`devin.devin_get_current_user`	Read	Get information about the currently authenticated Devin user. Use this to verify the API connection and identify which account is being used.

Related Devin Pages

Devin CLIUse direct JSON commands instead of MCP discovery. Devin MCPFull gateway reference and MCP tool names. KosmoKrator for Vercel AI SDKClient-level gateway setup.