Flyto Core

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/flytohub-flyto-core

About

Use cases: workflow-automation, browser-automation

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools

7 read · 2 write · 0 delete

Secrets

None asked for

Install scripts

None found

Runs as

Python package

Tools (9)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

• execute_module

  Execute a flyto-core module and return its output. This is the main action tool. ALWAYS call get_module_info first to know the required parameters. Returns: {ok: true, data: {...}} on success, {ok: false, error: '...'} on failure. BROWSER MODULE STRATEGY (important for E2E testing): - DEFAULT: Use DOM-based modules for accuracy. browser.extract → read text, attributes, element properties from DOM. browser.evaluate → run JavaScript to inspect page state, read DOM, check conditions. browser.snapshot → get full DOM structure (HTML/text) for analysis. browser.find → locate elements by sel…

• get_capability_manifest

  Get the deterministic capability manifest for this flyto-core installation (schema 'flyto.core.capability-manifest.v1'). Read-only: it describes what is installed, it does not start or change anything. Use this to check whether two workers expose the same modules, or to confirm a plugin's modules are actually loaded before depending on them. Returns: sorted module ids, capabilities with their providing module ids, categories with counts, loaded plugin ids/versions/module counts, the registry and core versions, and a stable SHA-256 'hash' over all of it. The hash is comparable across hosts — id…

• get_module_examples

  Get concrete usage examples for a module, showing exact parameter values and expected output. Use this if get_module_info's examples are not enough to understand usage.

• get_module_info

  Get the full specification of a module: parameter schema (names, types, required, defaults), output schema, and usage examples. ALWAYS call this before execute_module to know the exact parameters required. Returns: params_schema (JSON Schema), output_schema, examples with expected output.

• list_modules

  Description is built at runtime.

• list_recipes

  List all available flyto-core recipes (pre-built multi-step workflows). Each recipe is a YAML file that chains multiple modules together. Returns: recipe names, descriptions, and required args. Use run_recipe to execute a recipe by name.

• run_recipe

  Execute a flyto-core recipe (pre-built multi-step workflow) by name. Recipes chain multiple modules together (e.g., browser.launch → goto → extract → file.write). Call list_recipes first to see available recipes and their required args. Returns: per-step results with status and timing, plus output file paths.

• search_modules

  Search the flyto-core MODULE CATALOG by keyword. ⚠️ This searches automation modules ONLY — NOT the web. Do NOT use this to search for people, news, products, lyrics, weather, or any real-world info. For web search → use Browser Protocol: execute_module('browser.launch') → execute_module('browser.goto', {url: 'https://www.google.com/search?q=...'}) → execute_module('browser.snapshot'). Use search_modules ONLY when you need to find which automation module to use. Good examples: 'click button', 'send email', 'resize image', 'parse json'. Bad examples: person names, news topics, product names — t…

• validate_params

  Dry-run parameter validation for a module without executing it. Use this to check if your parameters are correct before running a destructive or slow operation. Returns: {valid: true} or {valid: false, errors: ['...']}.

Signals

Stars

484

Forks

84

Open issues

0

Contributors

10

Weekly downloads

175

Last commit

Oct 23, 2026 (6 days ago)

Last release

Aug 14, 2026 (2 months ago)

Last package publish

Sep 30, 2026 (28 days ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name

io.github.flytohub/flyto-core

Version

2.12.6

Auth

No auth

Packages

pypi flyto-core

License

Apache-2.0

Repository

github.com/flytohub/flyto-core

First seen

Oct 24, 2026

Last checked

Oct 24, 2026

Source

Official MCP Registrygithub-graphql