Emisso Connect
ai.emissoPublished by emisso.aiOfficial publisherv1.0.0Updated Oct 24, 2026
Connect AI agents to the legacy systems LATAM business runs on. Live in Chile: tax, banks, payroll.
Overview
Emisso Connect is a remote MCP endpoint that links AI assistants to legacy LATAM business systems such as tax, banking, and payroll.
- What you can do
- Emisso Connect is a hosted MCP server reached at a remote endpoint, intended to connect AI agents to the legacy systems that LATAM businesses run on. The registry description says it is live in Chile and covers tax, banks, and payroll. No tools, packages, or authentication details are listed in the supplied manifest, so the exact operations available are not documented here.
- When to use it
- Consider it when an assistant needs to work with Chilean business back-office systems, particularly tax, banking, or payroll data and processes. It is aimed at organizations already using those legacy systems rather than general-purpose tasks.
- Requirements
- A remote MCP client that supports streamable HTTP, plus network access to the provider's endpoint. The manifest declares no authentication, environment variables, or headers, and no packages; any account or credential requirements are not stated in the supplied information.
Installation
In SourceWeft
- Open Emisso Connect 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/ai.emisso%2Fconnect/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": {
"emisso-connect": {
"type": "http",
"url": "https://connect.emisso.ai/mcp"
}
}
}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.