Skip to main content
Tokenomist MCP also lets your AI assistant submit a token to Tokenomist’s self-listing platform on your behalf. Point your assistant at your tokenomics documentation — a whitepaper, docs site, or pasted text — and it extracts the allocation and vesting structure, shows you the result for confirmation, then creates and submits the listing.
These are the only write tools the Tokenomist MCP server exposes. Every other tool (see Tools & prompts) is read-only. Self-listing tools never touch on-chain state — they only create draft listing data on Tokenomist.

​
Prerequisites

  • A Tokenomist API key connected to your MCP client.
  • Your account’s email registered on the self-listing platform at listing.tokenomist.ai — this is a separate sign-up from your main Tokenomist account. Your assistant checks this for you and gives you the sign-up link if you aren’t registered yet.
  • Your tokenomics source material ready to share: a whitepaper URL, docs pages, or pasted text, plus the total token supply (needed to convert allocation percentages into token amounts).

​
How the workflow works

Ask your assistant to list your token — for example, “List my token on Tokenomist using our docs at https://mydocs.example.com/tokenomics”. It follows this sequence:
1

Registration check

The assistant calls self_listing_check_registration. If your email isn’t registered yet, it stops and gives you the listing.tokenomist.ai sign-up link — sign up and verify your email, then ask it to continue.
2

Gather details

The assistant asks for anything it can’t find in your sources: project description, status (pre-launch or launched), at least one team member, official website and X/Twitter links, token contract address and chain ID, business contact email, categories, and total supply. It also asks whether your token is listed on CoinGecko — if yes, it needs the CoinGecko ID; if no, it generates a manual token slug instead.
3

Extract allocations and vesting

The assistant reads your sources and builds an allocation/vesting table — splitting TGE unlocks from vested remainders, converting sub-percentages, and mapping terminology (e.g. “seed round” → PRIVATE_INVESTORS) to Tokenomist’s categories. It never invents numbers — anything not in your sources is flagged as an assumption or marked to-be-decided.
4

Review the draft

The assistant shows you the full extracted data — every field, every vesting tranche with percentages, dates, and cliffs — as a table, and asks for corrections before saving anything.
5

Create and save

Once you confirm, the assistant creates the project (or updates an existing draft, if one already exists for this token) and saves the vesting schedules. If anything fails validation, it fixes exactly the reported fields and retries — you don’t need to intervene unless it’s stuck.
6

Final review and submit

The assistant shows you the saved draft one more time and asks for explicit confirmation before submitting. Submission is final — vesting schedules can’t be edited afterwards.
After every create, update, or vesting save, the assistant will give you a link to listing.tokenomist.ai/v2 so you can visually verify the draft yourself before it’s submitted. Always check it — submission locks the vesting schedule permanently.

​
Tools

​
Project fields

Required to create a project: projectName, projectDescription, businessEmail, category (e.g. ["DeFi"]), projectStatus (PRE_LAUNCH or LAUNCHED), at least one team member, official links (website and X are required), and token info.
  • tokenName, tokenSymbol, tokenAddress, chainId — required.
  • tokenCreationMethod — coingecko or manual. Defaults to coingecko if omitted, so always set it explicitly for tokens not on CoinGecko.
  • coingeckoTokenId — required when tokenCreationMethod is coingecko (the slug in the coin’s CoinGecko URL, e.g. bitcoin).
  • customTokenId — required when tokenCreationMethod is manual; must match ^[a-z0-9-_]+$.
  • maxSupply, totalSupply, tge — optional.
Updating tokenInfo replaces it entirely — the assistant always resends every token field on update, since an omitted tokenCreationMethod silently resets to coingecko.
Each tranche needs allocationName, vestingName, vestingPercentage (a numeric string, e.g. "12.5"), vestingAmount, distributionTo, distributionMethod, vestingDescription, and color. Across all tranches in a project, vestingPercentage must sum to exactly 100, and vestingAmount must equal vestingPercentage × totalSupply ÷ 100.Unless a tranche is marked TBD (terms unknown), it also needs startVestingDate, endVestingDate, cliffPeriod + cliffPeriodUnit (DAY/WEEK/MONTH/YEAR), and vestingFrequency + vestingFrequencyUnit (DAILY/WEEKLY/MONTHLY/YEARLY).distributionTo is one of FOUNDER_TEAM, ADVISORS, MARKETING, COMMUNITY, PRIVATE_INVESTORS, PUBLIC_INVESTORS, LIQUIDITY, FOUNDATION, OTHERS. distributionMethod is one of AIRDROP, AUCTIONS, VESTING, MINING, YIELD_FARMING, INITIAL_LIQUIDITY, ACTIVITY_BASED, OTHERS.
self_listing_upsert_vesting replaces the complete set of vesting schedules every time it’s called — there’s no partial update.

​
Validation errors

If a create, update, or vesting call fails validation, the tool result includes the specific fields that failed (vesting errors reference a tranche by its zero-based position in the schedule list). The assistant fixes exactly those fields and retries — it doesn’t need to re-ask you for information it already has.

​
Example prompts

  • “List my token on Tokenomist — here’s our tokenomics doc: [URL]. Total supply is 1,000,000,000.”
  • “Am I registered on the self-listing platform yet?”
  • “Show me my draft listings.”
  • “Update my listing’s website link to https://mynewsite.example.com.”
  • “I’m ready — submit my listing.”