Can I use Paperspace as a CLI?

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

Can I expose Paperspace through MCP?

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

Where are Paperspace credentials stored?

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

Can I deny write access for Paperspace MCP tools?

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

productivity

Paperspace MCP Integration for LangChain

Connect Paperspace to LangChain through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 7 read 0 write Bearer token auth

Submit Paperspace feedback View package source

Connect Paperspace to LangChain

Bridge LangChain agents to local KosmoKrator integration tools through MCP or headless CLI calls.

Use the MCP gateway when the agent should discover tools, or wrap kosmo integrations:call for fixed chains. The gateway is local, scoped to this integration, and starts with --write=deny so LangChain can inspect read-capable tools without receiving write access by default.

Paperspace MCP Config for LangChain

Keep the gateway scoped to the integration and operation class needed by the chain.

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

Run the Gateway Manually

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

Why Use KosmoKrator Here

Scoped tools

Expose only Paperspace 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.

Paperspace Tools Visible to LangChain

LangChain sees stable MCP tool names generated from the Paperspace integration catalog.

MCP tool	Source function	Type	Description
`integration__paperspace__paperspace_list_machines`	`paperspace.paperspace_list_machines`	Read	List all GPU machines in the Paperspace account. Returns IDs, names, OS, machine type, state, and public IP address.
`integration__paperspace__paperspace_get_machine`	`paperspace.paperspace_get_machine`	Read	Get details for a specific Paperspace machine by ID. Returns full machine information including specs, state, and network configuration.
`integration__paperspace__paperspace_list_notebooks`	`paperspace.paperspace_list_notebooks`	Read	List all Gradient notebooks in the Paperspace account. Returns notebook IDs, names, cluster, machine type, and state.
`integration__paperspace__paperspace_list_datasets`	`paperspace.paperspace_list_datasets`	Read	List all datasets in the Paperspace account. Returns dataset IDs, names, storage usage, and creation dates.
`integration__paperspace__paperspace_list_projects`	`paperspace.paperspace_list_projects`	Read	List all Gradient projects in the Paperspace account. Returns project IDs, names, descriptions, and creation dates.
`integration__paperspace__paperspace_list_ssh_keys`	`paperspace.paperspace_list_ssh_keys`	Read	List all SSH keys in the Paperspace account. Returns key IDs, names, and fingerprints.
`integration__paperspace__paperspace_get_current_user`	`paperspace.paperspace_get_current_user`	Read	Get information about the current authenticated Paperspace user, including email, user ID, and team membership.

Related Paperspace Pages

Paperspace CLIUse direct JSON commands instead of MCP discovery. Paperspace MCPFull gateway reference and MCP tool names. KosmoKrator for LangChainClient-level gateway setup.