Skip to content

Developers

Your agent already knows GitHub. It cannot quote a shipment in Bogota.

Meteor connects to Claude, Cursor, Codex or your own code over MCP, REST API and SDK, with the Latin American connectors that are not in any other catalog.

Read the docs Configure the MCP server

Can I connect my AI agent to Wasi, TCC or Alegra?

Yes, through Meteor. Meteor exposes a remote MCP server authenticated with an API key, so Claude, Cursor, Codex or an agent of your own can operate the platform directly. The work against the local systems (the real estate CRM, the carrier, the invoicing tool) is done by a Met: your agent runs it and the Met uses the connectors it already has active. There is also a REST API and a TypeScript SDK if you would rather write the code yourself.

Three ways in, depending on who writes the code

  • MCP server

    For when the thing operating is an agent, not you. You add it as a remote server with your key in the header and it becomes available in Claude Code, Claude Desktop, Cursor, Windsurf and Cline; in Codex, through a stdio bridge. The tool catalog is filtered by the key's scopes: whatever the key cannot do, the agent never sees.

    Client-by-client configuration ES

  • REST API

    The public contract, with prefixed keys, granular scopes, idempotency and documented errors. It is the same surface the MCP server runs on underneath, so there are never two truths: what exists in the reference is what exists.

    API reference ES

  • TypeScript SDK

    Published on npm and generated from the same contract, with types for every resource. It also ships test keys so you can build without spending real Energy, and a CLI for the terminal.

    @meteor.ia/sdk on npm

The connectors that are not in any other catalog

Your agent only solves what it has an integration for, and Latin American software was left out of the ecosystem: none of these five has an MCP server from its own vendor, and the large automation catalogs do not carry them either. Meteor does, because it built them for its own operation.

  • Wasi

    Industry-specific

    21 real tools

    Colombia

  • Aveonline

    Shipping and logistics

    11 real tools

    Colombia

  • TCC

    Shipping and logistics

    13 real tools

    Colombia

  • HQ Rental Software

    Industry-specific

    8 real tools

  • SIESA

    Invoicing and ERP

    20 real tools

    Colombia

And the ones that do have a public alternative

These are not exclusive (several have their own MCP server) and they are here anyway, because what changes is not having the connector but that the same Met handling the conversation can use it.

See the full integration catalog

How it works today, without the polish

  • Your agent runs a Met. You hand it the job ("quote this shipment to Cali", "find two-bedroom apartments") and the Met, which has the connector active, does it and returns the result. That is published and running.
  • Calling each connector tool separately, not yet. The contract is designed (scopes, write-only credentials, curated provider errors) and it is not published. When it is, it will show up in the portal changelog, not on this page.
  • Credentials never come back. No response returns a credential, not even masked. What is observable is the state of the connection.
  • Every connector does less than it sounds like. The TCC connector quotes and tracks, but does not generate shipping labels. Wasi reads the portfolio and creates clients, but does not publish listings. Every integration record has its own section on what it does not do, and it is worth reading before you design around it.

What you need to issue your first key

An active Meteor account with API access: keys are issued from Settings → Developers, with granular scopes and test keys. If you would rather not carry a monthly fee, the US$0 Developer plan exists and is not for sale: it is granted by applying as a Tech Partner or a Startup Partner.

How to get the US$0 plan Plans for running a business

Where each thing lives, and which language it is in

The technical documentation lives in one place and is not duplicated here. This page tells you what exists; the portal tells you how it is done. Part of the portal is published in English and part only in Spanish, and each card below says which.

  • Guides

    Authentication, building a Met, running it, streaming, webhooks, events, errors and idempotency, limits. Twenty-one guides, in English.

  • Reference ES

    The full contract, generated from the code: resources, parameters, responses and scopes. Published in Spanish, with the field names in English.

  • MCP ES

    The exact configuration for Claude Code, Claude Desktop, Cursor, Windsurf, Cline and Codex, and the tool catalog by scope. In Spanish, with copy-paste config blocks.

  • Partner API ES

    The partner:* surface, exclusive to partner keys: attributed clients, opportunities, projects and payouts.

  • Changelog ES

    What changed in the contract and when. It is where direct connector calls will show up the day they exist.

  • Partner program

    If you are also going to implement for clients, the channel has its own program, with a portal, training and attribution.

Questions from people already building

The technical part, answered short

Meteor exposes a remote MCP server authenticated with an API key. You add it as a remote server in Claude Code, Claude Desktop, Cursor, Windsurf or Cline, and through a stdio bridge in Codex. The exact configuration for each client, with the URL and the header, lives in the documentation portal.

Yes, through a Met. Your agent runs a Met from the workspace, that Met has the connectors active, so it does the work against Wasi, TCC or Alegra and returns the result. Calling each connector tool individually from outside is designed and not yet published.

An active Meteor account with API access enabled. Keys are issued from Settings → Developers, with granular scopes and test keys. If you would rather not carry a monthly fee, the US$0 Developer plan is granted by applying as a Tech Partner or a Startup Partner.

Yes, a TypeScript SDK published on npm as @meteor.ia/sdk, generated from the same contract that serves the API. There is also a CLI and test keys so you can build without spending real Energy.

Here the connector is not a node you orchestrate step by step: it is a capability a Met uses when it needs to, inside a conversation or a task. And these connectors are local: carriers, invoicing and CRMs from Latin America that the large catalogs do not carry.

Yes. Partners also get their own API with partner:* scopes to query their attributed clients, their opportunities, their projects and their payouts, plus their own MCP server. It is documented in the portal.

Partly, and we would rather say so than let you find out. The portal landing and the 21 guides are in English. The API reference, the MCP client configuration, the partner API and the changelog are published in Spanish only. Every link on this page says which one you are opening.

Connect your agent in a few minutes

Your MCP client configuration, the reference and the SDK are all in the technical portal.

Go to the documentation portal Apply for the US$0 plan