Solana MCP Server

mint_tokens

Mint SPL tokens and send them to a destination wallet on Solana.

Instructions

Mint SPL tokens to a destination wallet. Requires PRIVATE_KEY with mint authority.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mint_address": "<mint_address>",
      "to_address": "<to_address>",
      "amount": "<amount>",
      "network": "<network>"
    },
    "name": "mint_tokens"
  }
}

Input Schema

Name	Required	Description
`mint_address`	Yes	Token mint address
`to_address`	Yes	Destination wallet address
`amount`	Yes	Amount of tokens to mint (UI amount)
`network`	Yes	Network — MUST be specified

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 27, 2026

TDQS

A3.9/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses auth requirement (PRIVATE_KEY) but no annotations exist. Does not mention side effects like token supply increase, transaction costs, or confirmation behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence plus requirement. Efficient, front-loaded, no excess words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Minimal description covers core action and auth. Lacks output/return info, which is typical for mutation tools with no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage 100% with descriptions. Description adds no extra parameter meaning beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States verb 'Mint', resource 'SPL tokens', and target 'destination wallet'. Clearly distinguishes from sibling tools like burn_tokens, create_token, transfer_token.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Specifies prerequisite 'Requires PRIVATE_KEY with mint authority', implying when to use. Lacks explicit alternatives, but context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.