General Tools
aviansuite.com
Provides general-purpose tools through the Model Context Protocol.
ENDPOINT 1
https://aviansuite.com/v1/install/mcp
MCP server metadata
- Name
- jaybase-install
- Version
- 0.1.0
You are setting up Avian Suite. Every free trial starts with 10 GB and needs no credit card. Talk in plain language. Use the say field. Show billing_url to the owner, but never open it, navigate to it, click it, or complete Stripe Checkout yourself. Never show or follow a Stripe Dashboard, API-key, or provider remediation link. Never say claim, token, MCP, bearer, plugin, JSON, or tenant. After the owner confirms the trial and you finish setup, they can add a payment method, change the plan, stop at period end, or add another agent.
Known tools 2
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.jaybase-install]
url = "https://aviansuite.com/v1/install/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"jaybase-install": {
"type": "http",
"url": "https://aviansuite.com/v1/install/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: jaybase-install
Remote MCP URL: https://aviansuite.com/v1/install/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": {
"jaybase-install": {
"url": "https://aviansuite.com/v1/install/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"jaybase-install": {
"type": "http",
"url": "https://aviansuite.com/v1/install/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "jaybase-install",
"transport": "streamable-http",
"url": "https://aviansuite.com/v1/install/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.