
Inttegro
com.inttegroPublished by inttegro.comOfficial publisherv0.1.1Updated Oct 27, 2026
Operate an Inttegro merchant account with authenticated commerce tools and confirmed actions.
Overview
Hosted Inttegro MCP server that lets an assistant operate a merchant's Inttegro commerce account through OAuth-authenticated tools.
- What you can do
- Run authenticated commerce operations against the Inttegro merchant account selected during authorization
- Work with live Inttegro tools packaged in the Inttegro agent plugin, alongside merchant workflows and specialist agents
- Rely on per-request checks of organization, membership and granular Inttegro scopes
- Use read-only diagnostics tooling from the same project family to inspect OAuth, endpoint protection and the tool catalog
- When to use it
- Use it when an assistant needs to act on an Inttegro merchant account, for example to run commerce operations or merchant workflows inside an AI client, rather than only reading documentation.
- Requirements
- A remote Streamable HTTP endpoint; nothing to install locally. A compatible MCP client that supports OAuth, plus an Inttegro account and completion of the Inttegro OAuth flow. Tools act on the organization chosen during authorization.
Installation
In SourceWeft
- Open Inttegro 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/com.inttegro%2Fmcp/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": {
"inttegro": {
"type": "http",
"url": "https://mcp.inttegro.com/"
}
}
}README
Inttegro AI
Open-source tools for bringing Inttegro into AI applications and agent workflows.
This repository is the public home for Inttegro agent plugins, reusable skills, protocol integrations, examples, and libraries that are useful beyond a single product or model provider. Host-specific packages stay thin: business logic, tenant isolation, and authorization policy remain in Inttegro's shared services.
Projects
Inttegro MCP
Inttegro hosts a remote Model Context Protocol server at:
Compatible clients authenticate with OAuth. The service checks the selected organization, membership, and granular Inttegro scopes on every request. API keys remain a separate workload credential for headless integrations and should never be pasted into an interactive AI conversation.
Connect an MCP client
Use the hosted Streamable HTTP endpoint; there is no local server to install:
Open the connection in a compatible client and complete the Inttegro OAuth flow. The tools then operate on the organization selected during authorization. See the connection guide for supported client packages and usage guidance.
Install Inttegro skills
Install the full Inttegro developer skill collection with the open-source skills CLI:
To install one skill, select it explicitly:
Browse the complete collection at skills.sh/inttegro/ai.
Install the Claude plugin
Then open /mcp in Claude Code and complete Inttegro sign-in.
Repository structure
plugins/— installable agent plugins and their host manifests.skills/— public developer skills for building and maintaining Inttegro integrations.packages/— libraries and protocol adapters suitable for independent versioning.examples/— small, runnable examples built on public Inttegro interfaces..claude-plugin/and.codex-plugin/— marketplace metadata for supported hosts.registry/— versioned discovery metadata for the official MCP Registry.scripts/— dependency-free consistency and package validation.
The hosted Inttegro platform, customer data, credentials, and internal operational tooling do not belong in this repository.
Development
Validate the current Claude marketplace and Inttegro plugin with:
See CONTRIBUTING.md before proposing a change. Security issues should be reported privately as described in SECURITY.md.
License
Unless a subdirectory says otherwise, this repository is available under the MIT License.
Source: README.md at commit 8cef967
Tools
0Version history
2- v0.1.1LatestOct 20, 2026
- v0.1.0Oct 15, 2026
Score
85% 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
- License10 pts