MCP.so
ログイン

AverbePorto MCP Server

@GHSix

基本情報

カテゴリ

その他

ライセンス

MIT license

トランスポート

stdio

作者

GHSix

AverbePorto MCP Server について

AverbePorto MCP Server

AverbePorto MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "AverbePorto-MCP": {
      "command": "npx",
      "args": [
        "-y",
        "@smithery/cli",
        "install",
        "@GHSix/averbeporto-mcp",
        "--client",
        "claude"
      ]
    }
  }
}

AverbePorto MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

上のボタンで一時的なサンドボックスでこのサーバーを実行し、ツール一覧を取得できます。

概要

What is AverbePorto-MCP?

The AverbePorto-MCP is an MCP server that integrates with the AverbePorto platform, facilitating access to authentication and document sending services through AI tools. It is aimed at users of the AverbePorto cargo insurance platform who need to interact with XML documents and ANTT protocols via AI assistants.

How to use AverbePorto-MCP?

Install via Smithery using npx -y @smithery/cli install @GHSix/averbeporto-mcp --client claude, or configure manually by adding the server to your MCP client's configuration file (Claude Desktop, Cursor, Roo Code, or GitHub Copilot) with the path to the build/index.js script and your AverbePorto API credentials.

Key features of AverbePorto-MCP

  • Authenticate on the AverbePorto platform via the login tool
  • Upload XML documents with optional recipient and version
  • Consult ANTT protocols by key or vice versa
  • Retrieve sent documents with various filters and pagination
  • Decompose 44-digit access keys for NF-e, CT-e, or MDF-e

Use cases of AverbePorto-MCP

  • Automating XML document upload to AverbePorto via AI assistants
  • Consulting ANTT protocol statuses programmatically
  • Retrieving and filtering cargo insurance averbação documents
  • Decomposing and analyzing electronic invoice access keys

よくある質問

1

What client applications does AverbePorto-MCP support?

Claude Desktop, Cursor, Roo Code, and GitHub Copilot.

2

What are the runtime requirements?

Node.js is required; the server is run using the command "node" with the path to build/index.js.

3

How are API credentials handled for GitHub Copilot?

Credentials are configured via environment variables (AVERBEPORTO_USER and AVERBEPORTO_PASS) and stored securely, with VS Code prompting for them on first run.

4

What document types are supported for retrieval?

DI, MDF-e, CT-e, NF-e, and Minuta CT-e.

5

What output formats are available for protocol consultation?

JSON, XML, and CSV.

コメント

「その他」の他のコンテンツ