Brightsy MCP Server
The Brightsy MCP Server acts as a bridge to an OpenAI-compatible AI agent, allowing you to:
Proxy Requests: Forward requests from an MCP client to a Brightsy AI agent using a customizable tool name (default is "brightsy").
Handle Structured Input: Process standard chat format inputs with
messagesarrays containingroleandcontentproperties.Configure Flexibly: Set up the server using either command-line arguments or environment variables.
Connect Securely: Use configurable credentials (agent ID and API key) to authenticate with the Brightsy AI agent.
Test Functionality: Utilize included scripts for both command-line and direct MCP protocol testing.
Allows forwarding requests to an Brightsy AI agent using an OpenAI-compatible format, enabling interaction with the agent through a standardized messages array with role and content properties.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Brightsy MCP Server Can you help me draft a professional email to schedule a meeting?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Brightsy MCP Server
This is a Model Context Protocol (MCP) server that connects to an Brightsy AI agent.
Installation
npm installRelated MCP server: AI Helper MCP Server
Usage
To start the server:
npm start -- --agent-id=<your-agent-id> --api-key=<your-api-key>Or with positional arguments:
npm start -- <your-agent-id> <your-api-key> [tool-name] [message]You can also provide an initial message to be sent to the agent:
npm start -- --agent-id=<your-agent-id> --api-key=<your-api-key> --message="Hello, agent!"Customizing the Tool Name
By default, the MCP server registers a tool named "brightsy". You can customize this name using the --tool-name parameter:
npm start -- --agent-id=<your-agent-id> --api-key=<your-api-key> --tool-name=<custom-tool-name>You can also set the tool name as the third positional argument:
npm start -- <your-agent-id> <your-api-key> <custom-tool-name>Or using the BRIGHTSY_TOOL_NAME environment variable:
export BRIGHTSY_TOOL_NAME=custom-tool-name
npm start -- --agent-id=<your-agent-id> --api-key=<your-api-key>Environment Variables
The following environment variables can be used to configure the server:
BRIGHTSY_AGENT_ID: The agent ID to use (alternative to command line argument)BRIGHTSY_API_KEY: The API key to use (alternative to command line argument)BRIGHTSY_TOOL_NAME: The tool name to register (default: "brightsy")
Testing the agent_proxy Tool
The agent_proxy tool allows you to proxy requests to an Brightsy AI agent. To test this tool, you can use the provided test scripts.
Prerequisites
Before running the tests, set the following environment variables:
export AGENT_ID=your-agent-id
export API_KEY=your-api-key
# Optional: customize the tool name for testing
export TOOL_NAME=custom-tool-nameAlternatively, you can pass these values as command-line arguments:
# Using named arguments
npm run test:cli -- --agent-id=your-agent-id --api-key=your-api-key --tool-name=custom-tool-name
# Using positional arguments
npm run test:cli -- your-agent-id your-api-key custom-tool-nameRunning the Tests
To run all tests:
npm testTo run specific tests:
# Test using the command line interface
npm run test:cli
# Test using the direct MCP protocol
npm run test:directTest Scripts
Command Line Test (
test-agent-proxy.ts): Tests the agent_proxy tool by running the MCP server with a test message.Direct MCP Protocol Test (
test-direct.ts): Tests the agent_proxy tool by sending a properly formatted MCP request directly to the server.
How the Tool Works
The MCP server registers a tool (named "brightsy" by default) that forwards requests to an OpenAI-compatible AI agent and returns the response. It takes a messages parameter, which is an array of message objects with role and content properties.
Example usage in an MCP client:
// Using the default tool name
const response = await client.callTool("brightsy", {
messages: [
{
role: "user",
content: "Hello, can you help me with a simple task?"
}
]
});
// Or using a custom tool name if configured
const response = await client.callTool("custom-tool-name", {
messages: [
{
role: "user",
content: "Hello, can you help me with a simple task?"
}
]
});The response will contain the agent's reply in the content field.
Available Tools
1 toolbrightsyC
Proxy requests to an Brightsy AI agent
Inputs: messages (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'brightsy' has a clear and distinct purpose as a proxy to the Brightsy AI agent.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The name 'brightsy' is straightforward and matches the server's purpose.
A single tool is generally too few for most server purposes, as it offers minimal functionality and can limit agent capabilities. While it might suffice for a simple proxy, it feels thin and under-scoped for typical MCP server expectations.
The tool surface is incomplete for a general-purpose AI agent proxy, lacking operations like configuration, status checks, or specific request types. However, the single tool covers the basic proxy function, leaving notable gaps but not entirely failing.
Maintenance
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Connect AI agents to Replynodes over the Model Context Protocol.
A Model Context Protocol server for Wix AI tools
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables role-based context management for AI agents, allowing users to establish specific instructions, maintain partitioned memory, and adapt tone for different agent roles in their system.1MIT
- FlicenseNot gradedqualityDmaintenanceA server that allows AI agents to consult multiple large language models (like Grok, Gemini, Claude, GPT-4o) through Model Context Protocol for assistance and information.4-

CodeAlive MCPofficial
AlicenseNot gradedqualityBmaintenanceA Model Context Protocol server that enhances AI agents by providing deep semantic understanding of codebases, enabling more intelligent interactions through advanced code search and contextual awareness.91MIT- AlicenseNot gradedqualityDmaintenanceA server that implements the Model Context Protocol, providing a standardized way to connect AI models to different data sources and tools.12MIT