Atla
OfficialThe Atla MCP Server enables standardized evaluation of LLM responses using Atla's evaluation models, providing scores and textual critiques based on specific criteria.
Evaluate LLM responses: Score and critique responses against single or multiple evaluation criteria simultaneously
Choose evaluation models: Use flagship (
atla-selene) or compact (atla-selene-mini) modelsCustomize evaluations: Optionally include original context and expected outputs
Integration options: Connect via OpenAI Agents SDK, Claude Desktop, or Cursor
Provides compatibility with the OpenAI Agents SDK, allowing users to connect to the Atla MCP server for LLM evaluation services.
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., "@Atlaevaluate my response to 'Explain quantum computing' for accuracy and clarity"
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.
Atla MCP Server
This repository was archived on July 21, 2025. The Atla API is no longer active.
An MCP server implementation providing a standardized interface for LLMs to interact with the Atla API for state-of-the-art LLMJ evaluation.
Learn more about Atla here. Learn more about the Model Context Protocol here.
Available Tools
evaluate_llm_response: Evaluate an LLM's response to a prompt using a given evaluation criteria. This function uses an Atla evaluation model under the hood to return a dictionary containing a score for the model's response and a textual critique containing feedback on the model's response.evaluate_llm_response_on_multiple_criteria: Evaluate an LLM's response to a prompt across multiple evaluation criteria. This function uses an Atla evaluation model under the hood to return a list of dictionaries, each containing an evaluation score and critique for a given criteria.
Related MCP server: Ollama MCP Server
Usage
To use the MCP server, you will need an Atla API key. You can find your existing API key here or create a new one here.
Installation
We recommend using
uvto manage the Python environment. See here for installation instructions.
Manually running the server
Once you have uv installed and have your Atla API key, you can manually run the MCP server using uvx (which is provided by uv):
ATLA_API_KEY=<your-api-key> uvx atla-mcp-serverConnecting to the server
Having issues or need help connecting to another client? Feel free to open an issue or contact us!
OpenAI Agents SDK
For more details on using the OpenAI Agents SDK with MCP servers, refer to the official documentation.
Install the OpenAI Agents SDK:
pip install openai-agentsUse the OpenAI Agents SDK to connect to the server:
import os
from agents import Agent
from agents.mcp import MCPServerStdio
async with MCPServerStdio(
params={
"command": "uvx",
"args": ["atla-mcp-server"],
"env": {"ATLA_API_KEY": os.environ.get("ATLA_API_KEY")}
}
) as atla_mcp_server:
...Claude Desktop
For more details on configuring MCP servers in Claude Desktop, refer to the official MCP quickstart guide.
Add the following to your
claude_desktop_config.jsonfile:
{
"mcpServers": {
"atla-mcp-server": {
"command": "uvx",
"args": ["atla-mcp-server"],
"env": {
"ATLA_API_KEY": "<your-atla-api-key>"
}
}
}
}Restart Claude Desktop to apply the changes.
You should now see options from atla-mcp-server in the list of available MCP tools.
Cursor
For more details on configuring MCP servers in Cursor, refer to the official documentation.
Add the following to your
.cursor/mcp.jsonfile:
{
"mcpServers": {
"atla-mcp-server": {
"command": "uvx",
"args": ["atla-mcp-server"],
"env": {
"ATLA_API_KEY": "<your-atla-api-key>"
}
}
}
}You should now see atla-mcp-server in the list of available MCP servers.
Contributing
Contributions are welcome! Please see the CONTRIBUTING.md file for details.
License
This project is licensed under the MIT License. See the LICENSE file for details.
Available Tools
2 toolsevaluate_llm_responseA
Evaluate an LLM's response to a prompt using a given evaluation criteria.
This function uses an Atla evaluation model under the hood to return a dictionary
containing a score for the model's response and a textual critique containing
feedback on the model's response.
Returns:
dict[str, str]: A dictionary containing the evaluation score and critique, in
the format `{"score": <score>, "critique": <critique>}`.
| Name | Required | Description | Default |
|---|---|---|---|
| evaluation_criteria | Yes | The specific criteria or instructions on which to evaluate the model output. A good evaluation criteria should provide the model with: (1) a description of the evaluation task, (2) a rubric of possible scores and their corresponding criteria, and (3) a final sentence clarifying expected score format. A good evaluation criteria should also be specific and focus on a single aspect of the model output. To evaluate a model's response on multiple criteria, use the `evaluate_llm_response_on_multiple_criteria` function and create individual criteria for each relevant evaluation task. Typical rubrics score responses either on a Likert scale from 1 to 5 or binary scale with scores of 'Yes' or 'No', depending on the specific evaluation task. | |
| llm_prompt | Yes | The prompt given to an LLM to generate the `llm_response` to be evaluated. | |
| llm_response | Yes | The output generated by the model in response to the `llm_prompt`, which needs to be evaluated. | |
| expected_llm_output | No | A reference or ideal answer to compare against the `llm_response`. This is useful in cases where a specific output is expected from the model. Defaults to None. | |
| llm_context | No | Additional context or information provided to the model during generation. This is useful in cases where the model was provided with additional information that is not part of the `llm_prompt` or `expected_llm_output` (e.g., a RAG retrieval context). Defaults to None. | |
| model_id | No | The Atla model ID to use for evaluation. `atla-selene` is the flagship Atla model, optimized for the highest all-round performance. `atla-selene-mini` is a compact model that is generally faster and cheaper to run. Defaults to `atla-selene`. | atla-selene |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
evaluate_llm_response_on_multiple_criteriaA
Evaluate an LLM's response to a prompt across multiple evaluation criteria.
This function uses an Atla evaluation model under the hood to return a list of
dictionaries, each containing an evaluation score and critique for a given
criteria.
Returns:
list[dict[str, str]]: A list of dictionaries containing the evaluation score
and critique, in the format `{"score": <score>, "critique": <critique>}`.
The order of the dictionaries in the list will match the order of the
criteria in the `evaluation_criteria_list` argument.
| Name | Required | Description | Default |
|---|---|---|---|
| evaluation_criteria_list | Yes | ||
| llm_prompt | Yes | The prompt given to an LLM to generate the `llm_response` to be evaluated. | |
| llm_response | Yes | The output generated by the model in response to the `llm_prompt`, which needs to be evaluated. | |
| expected_llm_output | No | A reference or ideal answer to compare against the `llm_response`. This is useful in cases where a specific output is expected from the model. Defaults to None. | |
| llm_context | No | Additional context or information provided to the model during generation. This is useful in cases where the model was provided with additional information that is not part of the `llm_prompt` or `expected_llm_output` (e.g., a RAG retrieval context). Defaults to None. | |
| model_id | No | The Atla model ID to use for evaluation. `atla-selene` is the flagship Atla model, optimized for the highest all-round performance. `atla-selene-mini` is a compact model that is generally faster and cheaper to run. Defaults to `atla-selene`. | atla-selene |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
2 tool updates
v1.0.0- Added
evaluate_llm_response - Added
evaluate_llm_response_on_multiple_criteria
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one evaluates a single criterion, the other evaluates multiple criteria. Their names and descriptions make the difference unambiguous.
Both tool names follow a consistent verb_noun_qualifier pattern, starting with 'evaluate_llm_response' and differentiating with '_on_multiple_criteria'. No mixing of conventions.
With only 2 tools, the server feels thin. While the tools cover the core evaluation functionality, a typical well-scoped server has 3-15 tools, making this borderline insufficient.
The tools provide basic evaluation for single and multiple criteria, but lack supporting tools such as managing criteria, listing models, or retrieving history. The surface is minimal and may leave agents with limited options.
Maintenance
Related MCP Connectors
MCP server providing access to the Scorecard API to evaluate and optimize LLM systems.
MCP server for building and testing AI agents with multi-model experimentation and insights.
MCP server for AI dialogue using various LLM models via AceDataCloud
Related MCP Servers
- AlicenseBqualityDmaintenanceAn MCP server that provides LLMs access to other LLMs438 npm81MIT
- FlicenseNot gradedqualityDmaintenanceA server that enables seamless integration between local Ollama LLM instances and MCP-compatible applications, providing advanced task decomposition, evaluation, and workflow management capabilities.6-
- AlicenseAqualityDmaintenanceAn MCP server that enables LLMs to interact with Agent-to-Agent (A2A) protocol compatible agents, allowing for sending messages, tracking tasks, and receiving streaming responses.528MIT

multivon-mcpofficial
AlicenseAqualityBmaintenanceMCP server that gives AI coding agents direct access to evaluation tools.23Apache 2.0