Tinyman MCP Server

Most developer tooling work still happens through a UI a human drives. Tinyman MCP MCP server moves it into the conversation instead. Tinyman Model Context Protocol Implementation.

The short version

This project provides MCP tools and resources for interacting with Tinyman AMM protocol on Algorand blockchain. It consists of two main packages:

The tools it exposes

The server publishes 9 tools. What each one is for:

• tinyman_get_pool — Retrieve detailed information about a specific pool
• tinyman_get_pool_analytics — Get analytics and statistics for a pool
• tinyman_get_pool_creation_quote — Generate quote for creating a new pool
• tinyman_get_swap_quote — Generate quotes for asset swaps with support for:
• tinyman_get_liquidity_quote — Generate quotes for adding liquidity
• tinyman_get_remove_liquidity_quote — Generate quotes for removing liquidity
• tinyman_get_asset_optin_quote — Generate quote for opting into an asset
• tinyman_get_validator_optin_quote — Generate quote for opting into a validator
• tinyman_get_validator_optout_quote — Generate quote for opting out of a validator

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

What it needs from you

Configuration is passed through the environment: ALGORAND_NETWORK, ALGORAND_ALGOD_API, ALGORAND_ALGOD, ALGORAND_ALGOD_PORT, ALGORAND_TOKEN, ALGORAND_AGENT_WALLET, ITEMS_PER_PAGE. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Tinyman MCP's toolset — tinyman_get_pool, tinyman_get_pool_analytics, tinyman_get_pool_creation_quote and 6 more — is a fair guide to whether it matches your workflow. It is maintained by GoPlausible; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Tinyman MCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.