MCP.so
Sign In

Servidor TESS com Suporte a MCP Server

@diegofornalha

Basic information

Category

Other

Transports

stdio

Author

diegofornalha

About Servidor TESS com Suporte a MCP Server

Extensão XTP para o servidor MCP-TESS - Integração da API TESS com XTP

Servidor TESS com Suporte a MCP Server config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

Servidor TESS com Suporte a MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Servidor TESS com Suporte a MCP?

It is a proxy server that integrates TESS (Text Evaluation and Semantic Services) with the MCP (Multi-Channel Platform). It is built with Node.js + Express and uses a Rust/WebAssembly plugin for core logic, acting as a proxy to MCP.run.

How to use Servidor TESS com Suporte a MCP?

Install dependencies with npm install, configure environment variables in .env (PORT, MCP_API_KEY, MCP_API_URL, MCP_SSE_URL), build the WebAssembly plugin with npm run build, then start the server with npm start (or npm run dev for hot‑reload). Use endpoints: GET /health for health check, GET /api/mcp/tools to list tools, POST /api/mcp/execute to execute a tool (requires session_id and optional mcp_sse_url as query parameters).

Key features of Servidor TESS com Suporte a MCP

  • Integrates TESS with the Multi‑Channel Platform (MCP)
  • Node.js + Express server with Rust/WebAssembly plugin
  • Proxies requests to MCP.run (via SSE)
  • Health check endpoint at GET /health
  • Listing and executing MCP tools via REST API
  • Hot‑reload development mode available

Use cases of Servidor TESS com Suporte a MCP

  • Expose MCP tools through a local HTTP proxy
  • Automate or integrate TESS evaluations with MCP workflows
  • Debug and test MCP interactions using a simple REST interface
  • Monitor server availability with the health check endpoint

Frequently asked questions

1

What are the runtime requirements?

Node.js 18+, Rust with Cargo, and the `wasm32-wasi` target installed (`rustup target add wasm32-wasi`).

2

How do I configure the server?

Set environment variables in a `.env` file: `PORT`, `MCP_API_KEY`, `MCP_API_URL`, and `MCP_SSE_URL`.

3

How do I build and run the server?

Build the WebAssembly plugin with `npm run build`, then start with `npm start`. For development with hot‑reload, use `npm run dev`.

4

What security measures are in place?

All requests must include a valid `session_id`. MCP credentials are set via environment variables, and CORS is enabled for development.

5

How do I troubleshoot common issues?

Check that the plugin compiled correctly, confirm environment variables are set, review server logs, and ensure MCP.run is accessible.

Comments

More Other MCP servers