English Français العربية

Workflow

Registre officiel IA et agents

Create, browse, remix, collaborate on, and run durable AI workflow nodes from MCP hosts.

Code source Site web Documentation

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http workflow 'https://tinyassets.io/mcp-directory'
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "workflow": {
            "type": "http",
            "url": "https://tinyassets.io/mcp-directory"
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. TinyAssets
  2. Try it
  3. Direction
  4. Links
  5. Contributing
  6. License

TinyAssets

An agent of your own in the chat bubble: connect any model source, then build what you need from there.

Try it

The hosted app is the supported way in. Android is in a closed Google Play test, not a public store listing. The steps, what to expect, and how to report a bug are in docs/getting-started/testers.md.

You connect your own model subscription. This project does not supply a model. What is free, and what is not built yet, is on https://tinyassets.io/fine-print/.

Running the production server on your own machine is not a supported install. Status: docs/getting-started/self-hosting.md.

Direction

The founder owns this section. To re-steer, replace a line; never add one beside it. python scripts/sync_direction.py copies it verbatim into AGENTS.md.

  1. Product: a default bubble agent that continuously matches and beats the industry-leading main agents (Grok Bot, Muse, ChatGPT dots, Claude), built as a starter package on a pi.dev-modelled harness; users customize the harness and interface to build anything.
  2. Plumbing: the model sees 4 tools (read/write/edit/bash) plus ta; one extension unit; one agent definition for every model provider; no provider-specific code.
  3. The agent's abilities are editable files, skills and packages. The platform does not build feature editors or pre-built features.
  4. Users connect any model source; default to their strongest connected source.
  5. Foundational patches are brought FORWARD, so pre-migration band-aids never delay positive architectural moves. Weigh the totality of pending work, so each module is always pursuing or maintaining its best architecture, and refactor and reorder the remaining work to get there. (Today that foundation is per-owner isolation, as one clean cutover: the isolated path is the only path, one migration in a short maintenance window after a full backup, and cross-owner app checks the OS now enforces are deleted in the same change.)
  6. Ship live fast and verify live. LESS process: delete stale docs, tests and notes rather than adding more.
  7. Long-term goal: in both the Google Play and Apple App Store, and listed in the major agents' connector directories (Meta Muse, ChatGPT, Claude) so users find TinyAssets by search, not only as a custom connector, with growing downloads and positive reviews.
  8. 24/7 uptime with zero hosts online: every surface works with no host machine on.

No longer the direction: "a global goals engine", Goal ladders, and fantasy as the default domain. Where any older doc disagrees with this section, this section wins.

Contributing

Python 3.11+. Tests run offline; providers are mocked, so no API keys are needed. How to contribute, and what this repo does not promise, is CONTRIBUTING.md.

git clone https://github.com/TinyAssets/TinyAssets.git
cd TinyAssets
python -m venv .venv && source .venv/bin/activate   # Windows: .venv\Scripts\activate
pip install -e ".[dev]"
python -m scripts.ci_structural_guards               # the fast guards every PR runs
pytest -q tests/test_<area>.py                       # the tests your change touches
ruff check <changed files>

CI runs the rest. How work is done here: AGENTS.md.

License

MIT — see LICENSE. Built by Jonathan Farnsworth (jonathan.m.farnsworth@gmail.com, @Jonnyton); the only co-authors are the project's own AI agents.

Questions fréquentes

Qu'est-ce que Workflow ?

Create, browse, remix, collaborate on, and run durable AI workflow nodes from MCP hosts.

Comment installer Workflow ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http workflow 'https://tinyassets.io/mcp-directory'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour Workflow ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

Workflow est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient Workflow ?

Il est publié par Jonnyton. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.