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 you connect to by signing in or 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) can be done by a Met, which your agent runs and which uses the connectors it already has active, or by your own code calling a connector's tools one by one. There is also a REST API and a TypeScript SDK if you would rather write the code yourself.

If the question is not which connector exists but whether to build the agentic layer yourself, see Meteor for product teams.

Three ways in, depending on who writes the code

MCP server

For when the thing operating is an agent, not you. It brings 166 MCP tools to operate and also to build: it creates and tunes Mets, assembles flows, schedules automations and creates collections. You add it as a remote server in Claude Code, Claude Desktop, Cursor, Windsurf and Cline (in Codex, through a stdio bridge) and connect by signing in to Meteor or with your key in the header. The catalog is filtered by the key's scopes or the permissions you approved: whatever it cannot do, the agent never sees.
Client-by-client configuration ES
REST API

The public contract, 402 public operations 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

Sell and serve

21 real tools

Colombia
Aveonline

Run stores and orders

11 real tools

Colombia
TCC

Run stores and orders

23 real tools

Colombia
HQ Rental Software

Run stores and orders

8 real tools
SIESA

Collect and manage

26 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

To compare capabilities, markets and conditions before you design, use the capability registry or consume its structured JSON data.

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.
Or your code calls a connector tool directly. Without a Met in between: your code lists a connector's tools and runs the one it needs, with a live key that carries the integrations:execute scope. Test keys do not run connector tools or send messages.
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. The guides are 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: new operations, MCP tools and events, each with its date.
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 with 166 MCP tools. You add it as a remote server in Claude Code, Claude Desktop, Cursor, Windsurf or Cline, and through a stdio bridge in Codex. You connect by signing in to Meteor from the client (OAuth with dynamic registration, no key) where the client supports it, or with an API key in the header. The exact configuration for each client lives in the documentation portal.

Yes, in two ways. Your agent runs a Met from the workspace that has the connectors active, and the Met does the work against Wasi, TCC or Alegra and returns the result. Or your code calls a connector tool directly, one by one and without a Met in between, with a live key that carries the integrations:execute scope. Test keys do not run connector tools.

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. If you are an approved Tech Partner, you create your clients’ accounts from the API, pay for them with your own card and hand them over, and your partner key only operates the accounts attributed to you, checked on every call. 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 all documented in the portal.

Partly, and we would rather say so than let you find out. The portal landing and the 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.