Docs menu

Token mint

Solana token metadata

Set or update a Solana token's on-chain name, symbol, and logo, non-custodially. Supports both classic SPL Token (via Metaplex Token Metadata) and Token-2022 mints (via their built-in metadata extension). SolKnife hosts nothing: your JSON and image stay on a host you control.

Open the tool

Step by step: how to add metadata to a Solana token.

Features

  • Add a name, symbol, and logo to any SPL Token or Token-2022 mint
  • Built-in Arweave uploader: pick an image, SolKnife builds the JSON and fills the URI for you
  • Update existing metadata (until marked immutable)
  • Auto-detects whether to use Metaplex Token Metadata or the Token-2022 metadata extension
  • Reads the on-chain authority state and tells you what your wallet can change
  • Non-custodial: your wallet signs every transaction, SolKnife hosts nothing

How it works

Paste a token mint. SolKnife reads it and tells you whether metadata already exists, what it says, and whether your wallet can change it. Fill in the name, symbol, and a public URL to a JSON file (which you host) holding the image and description, then your wallet signs. SolKnife writes the right kind of metadata for the token program automatically and never handles your image or files. A small flat fee is shown before you sign.

Fees

A small flat SolKnife fee, rent for the metadata storage, and the Solana network fee. Hosting the JSON file and the image is separate; the Arweave upload tool can do it. Current amounts are on the pricing page.

API and MCP

Everything the page does is callable over HTTP, or as a tool on the MCP server at /api/mcp. Authentication and payment are in the agent docs.

GET /api/token-metadata/state

Read a mint's current on-chain Metaplex metadata.

MCP tool solknife_token_metadata_read · inputs mint

POST /api/token-metadata/build

Build an unsigned set/update metadata tx.

MCP tool solknife_token_metadata_build · inputs mint, owner, name, symbol, uri

POST /api/token-metadata/execute

Submit the signed metadata tx.

MCP tool solknife_token_metadata_execute · inputs signedTransaction, lastValidBlockHeight

Errors

A failed call returns { ok: false, error: { code, message } }. The codes: invalid-input (400), not-found (404), rate-limited (429), upstream-error (502), degraded (503). A rate-limited error can carry retryAfter, in seconds.

Key terms

Metadata URI
A link to a JSON file (which you host) holding the token's image and description. SolKnife writes the link on-chain but never hosts the file.
Update authority
The address allowed to change a token's metadata after it is created. SolKnife sets it to your wallet when it creates metadata.
Immutable
Locked metadata can never be changed again, by anyone. The lock is optional and permanent.
Metaplex Token Metadata
The original Solana metadata standard for fungible tokens and NFTs: a separate PDA account holds the metadata record alongside the mint. Used for classic SPL Token mints.
Token-2022 metadata extension
The newer in-mint metadata for Token-2022, stored inside the mint account itself instead of a separate PDA. Cheaper rent, but only available for Token-2022.

Frequently asked

How do I add a name and symbol to my Solana token?

Paste the mint address into this tool, connect the wallet that is the mint or update authority, fill in the name and symbol plus a public URL to a JSON file holding the image, then sign one transaction. SolKnife writes the right kind of metadata for the token program (Metaplex for SPL Token, the metadata extension for Token-2022) and never handles your image or files.

Does this work for both SPL Token and Token-2022?

Yes. SolKnife reads which program owns the mint and writes the matching record: a Metaplex metadata account for SPL Token, the metadata extension inside the mint for Token-2022. There is no setting for it.

Can I add a logo to a Solana token without writing any code?

Yes, without leaving this page. Below the URI field there's a built-in builder: upload an image, add an optional description and socials, and SolKnife uploads the image to Arweave, generates the Metaplex-shape JSON, uploads that too, and fills the URI field for you. Your wallet pays Irys directly; nothing routes through SolKnife. Or, if you already have a JSON hosted elsewhere, paste its URL into the URI field as before.

Can I update token metadata after I set it?

Yes, as long as the metadata is not marked immutable and your wallet is the current update authority. The same tool handles updates: it reads the current state, you change individual fields, your wallet signs. Marking metadata immutable is one-way and permanent, so do that only when the branding is final.

Why does my Solana token show as just an address in my wallet?

Because no metadata is attached to the mint yet. Wallets and explorers render name, symbol, and image from the mint's metadata account; with none, all they have is the raw mint address. Adding metadata with this tool fixes the display within a block or two of confirmation.

Do I need to be the mint authority to set metadata?

For a token with no metadata yet, the mint authority creates the metadata record. For an existing record, the update authority changes it. SolKnife reads the mint and tells you which role you hold, and whether your wallet can make the change you want, before you sign.

Where should I host the metadata JSON and image?

Anywhere that serves the file at a stable public URL. Permanent storage (Arweave, pinned IPFS) cannot go offline; a plain web host can. SolKnife never hosts anything for you; its Arweave upload tool pays Irys from your wallet.