General Tools
aerostator.com
Provides general-purpose tools through the Model Context Protocol.
ENDPOINT 1
https://aerostator.com/mcp
MCP server metadata
- Name
- emotres
- Version
- stage3-discovery
AeroStator (aerostator.com): permanent-magnet motor / generator catalog, saved FEM results, draft designs from requirements and 2-D FEM simulations on the user's own queue. Without sign-in only the public tools work: describe_service, list_capabilities, list_calculation_types, get_input_requirements, how_to_authenticate, start_sign_up. Everything that touches the user's machines, drafts, jobs or simulations needs an OAuth sign-in: when an answer says authentication_required, relay its data.user_message and let the user click Connect / Sign in in this app (the page also offers Create account). Never ask for a password in chat. Signed in: start with check_fit, or start_design when nothing fits; if an answer says needs_input, ask the engineer. Read emotres://guide.
Known tools 6
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.emotres]
url = "https://aerostator.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"emotres": {
"type": "http",
"url": "https://aerostator.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: emotres
Remote MCP URL: https://aerostator.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"emotres": {
"url": "https://aerostator.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"emotres": {
"type": "http",
"url": "https://aerostator.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "emotres",
"transport": "streamable-http",
"url": "https://aerostator.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.