Antò
fr.heyantoPublished by heyanto.frOfficial publisherv1.0.0Updated Oct 24, 2026
AI copilot for artisan food makers — stock, orders, HACCP and billing from your chat.
Overview
Antò is a remote MCP copilot that lets an assistant help artisan food makers manage stock, orders, HACCP records and billing from chat.
- What you can do
- Antò is a hosted MCP endpoint aimed at artisan food producers. According to its registry description, it acts as an AI copilot covering stock, orders, HACCP (food-safety) records and billing, driven from a chat conversation. The manifest lists no individual tools, so the exact operations available are not documented here.
- When to use it
- Consider it if you run a small food-production business and want an assistant to help with inventory, customer orders, food-safety paperwork and invoicing in one place. It is less relevant if you only need general-purpose tools or do not handle food-safety or billing records.
- Requirements
- A remote MCP server reached over streamable HTTP at its hosted endpoint; no local package or runtime is needed. OAuth authentication is required, so you need an account with the provider and must complete its sign-in flow. No environment variables or headers are declared.
Installation
In SourceWeft
- Open Antò in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/fr.heyanto%2Fanto/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"ant": {
"type": "http",
"url": "https://mcp.heyanto.fr/mcp/v1"
}
}
}Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.