Labsco
MCP SERVER

Arcontextify

by aorumbayev

Turn an ARC-56 contract spec into a runnable MCP server whose tools are the contract's own methods.

Chain State, Explorers & Contract Tooling
Summary
The contract spec becomes the tool list, so there is no wrapper to write.

If you already produce an ARC-56 spec as part of your build, that file is enough to get an agent calling the contract, and the read-only variant gives you a server that has no key to sign with. The author calls it an experimental proof of concept, so read the generated project before you point it at a contract holding value.

What it is

A command-line generator for Algorand. Point it at an ARC-56 contract specification and it writes out an MCP server project for that contract, with the contract's methods as tools alongside a few for state and connectivity. The author describes it as an experimental proof of concept rather than production software.

What you get
  • One server per contract, generated from the spec instead of hand-written
  • The contract's own methods exposed as tools, with simulation support so a call can be tried before it is sent
  • A choice at generation time of read-only calls, write-only calls, or both
  • Global application state and any account's local state, read on demand
  • An environment check and a connection status tool, so a misconfigured node shows up before the first contract call
  • Secrets read from the environment, with a dummy account standing in for read-only work — a private key is only needed if you generate the write side
  • A client configuration example bundled with the generated project
Requirements

Python with the uv package manager and AlgoKit Utils; the generator itself installs from PyPI with pipx or uv. The server it produces reads your Algorand node address and token from the environment, plus a delegated private key when you want it to submit write calls.

Setup effort

One command — pipx install arcontextify