Pictor MCP Server

Pictor MCP lets you connect your Pictor GPU cloud account to Claude so you can inspect GPU plans, check availability, manage instances, view logs, and manage SSH keys directly from a Claude conversation.

The connector uses the Model Context Protocol (MCP) over HTTPS and OAuth. Claude only receives access after you authorize the connection with your Pictor account.

MCP Server URL

Use this URL when adding Pictor as a custom connector in Claude:

https://apiv2.pictor.network/mcp

Before You Connect

You need:

• A Pictor account.

• The email on your Pictor account must be current and accessible.

• Your account must have enough balance or credit before creating or extending GPU instances.

• At least one SSH public key in Pictor if you want to create instances with SSH access.

If you use a team workspace, make sure your Pictor user is a member of the team before asking Claude to manage team resources.

Connect Pictor to Claude

1. Open Claude.

2. Go to Settings.

3. Open Connectors.

4. Choose Add custom connector.

5. Enter the MCP server URL:

https://apiv2.pictor.network/mcp

1. Continue to authorization.

2. Sign in with the email linked to your Pictor account.

3. Review the requested permissions.

4. Approve the connection.

After authorization, you can ask Claude to use your Pictor GPU account.

Available Tools

GPU Catalog

• list-gpus: Lists available GPU plans and catalog entries.

• check-gpu-availability: Checks whether a GPU type, count, and region are available.

GPU Instances

• list-my-instances: Lists GPU instances available to your account or team.

• get-instance-detail: Gets details for one GPU instance.

• create-instance: Creates a new GPU instance.

• start-instance: Starts a stopped or paused instance.

• stop-instance: Stops a running instance.

• enable-instance-auto-renew: Enables auto-renew for an instance.

• disable-instance-auto-renew: Disables auto-renew for an instance.

• add-instance-hours: Adds runtime hours to an instance.

• rename-instance: Changes an instance display name.

• delete-instance: Deletes an instance.

• get-instance-logs: Gets logs for an instance.

• add-ssh-keys-to-instance: Attaches SSH keys to an instance.

SSH Keys

• list-ssh-keys: Lists SSH keys in your account or team.

• create-ssh-key: Adds a new SSH public key.

• update-ssh-key: Updates an SSH key name or public key.

• delete-ssh-key: Deletes an SSH key.

Account

• get-user-balance: Shows your balance and credit. For team usage, Claude can request the team context if you provide a team ID.

InFlow Transactions

• create-inflow-checkout: Creates an InFlow checkout request.

• verify-inflow-transaction: Verifies an InFlow transaction and credits the matching Pictor user after completion.

• sync-pending-inflow-transactions: Syncs pending InFlow transactions.

Example Prompts

List available GPU plans:

Show me the available GPU plans with at least 24 GB VRAM.

Check availability:

Check if 1 GPU of plan ID 12 is available in the US region.

List instances:

List my current GPU instances.

Inspect an instance:

Show details for instance 123.

Create an instance:

Create a Linux GPU instance using GPU plan 12, 1 GPU, 150 GB storage, 24 hours duration, and SSH key ID 4.

View logs:

Show the latest logs for instance 123.

Stop an instance:

Stop instance 123.

Add runtime:

Add 12 hours to instance 123.

Rename an instance:

Rename instance 123 to training-a100-prod.

List SSH keys:

List my SSH keys.

Create an SSH key:

Add this SSH public key to my account and name it workstation:
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAA...

Check balance:

Show my Pictor balance and credit.

Team Usage

If you want Claude to manage team resources, include the team ID in your request:

List GPU instances for team ID 12.

Claude will pass the team ID to Pictor. Pictor verifies that your authenticated account has access to that team before running the tool.

Permissions and Safety

Read-only actions such as listing GPUs, listing instances, getting logs, and checking balance are marked as read-only.

Actions that create, update, stop, delete, extend, or otherwise change resources are marked as action tools and may require confirmation in Claude.

Claude should ask for confirmation before destructive or state-changing operations such as deleting an instance, deleting an SSH key, creating a checkout, or crediting a completed transaction.

Common Errors

401 invalid_token

Your Claude connection token is missing, expired, or does not match the MCP server URL.

Try disconnecting and reconnecting the Pictor connector in Claude.

403 insufficient_scope

Claude is connected, but the authorization token does not include the permission needed for that tool.

Reconnect the connector and approve the requested permissions.

redirect_uri is not registered

The OAuth redirect URI used by the client is not allowed.

If you are using Claude, reconnect through Claude settings. If you are testing manually, make sure your OAuth client registration includes the same redirect URI used during authorization.

Method not allowed

The MCP endpoint only accepts MCP protocol requests over POST.

Opening https://apiv2.pictor.network/mcp directly in a browser may show a method error. Test through Claude or an MCP client.

Instance not found

The instance ID is invalid, deleted, or belongs to another account or team.

Check your instance list and confirm the team ID if you are using team resources.

insufficient balance

Your Pictor account does not have enough balance or credit for the requested operation.

Add funds or reduce the requested GPU count, storage, or duration.

SSH access problems

Make sure your SSH public key is added to Pictor and attached to the target instance.

Support

For help with the Pictor MCP connector, contact:

[email protected]

When contacting support, include:

• Your Pictor account email.

• The Claude connector action you tried.

• The instance ID or team ID, if relevant.

• The error message shown in Claude.