Skip to main content
Glama
Public Gateway MCP

Public Gateway MCP

Official
by Axcient

Public Gateway MCP connects your favorite AI assistants directly to Axcient. Ask questions, pull insights, and take action β€” all through natural conversation. No dashboards to hunt through. No context switching. Just answers. πŸš€


✨ Why you'll love it

  • πŸ”Œ Plug and play β€” Drop it into Cursor, Claude Desktop, or any MCP-compatible client and go.

  • πŸ“‘ Real data, real time β€” Your AI tools work with live Axcient information, not stale snapshots.

  • πŸ› οΈ Built for builders β€” Designed for teams who want their agents to do things, not just talk about them.


Related MCP server: Autotask MCP Server

πŸš€ Quick start

Prerequisites

Install

git clone https://github.com/axcient/public-gateway-mcp.git
cd public-gateway-mcp
direnv allow

Configure

Add your Axcient API key to the .env file:

API_KEY="your-api-key-here"

Run

just run

That's it. Your MCP server is live. πŸŽ‰


πŸ€– Connect your AI client

Add Public Gateway MCP to your MCP client configuration and point it at the running server. Once connected, your assistant can interact with Axcient on your behalf.

πŸ’‘ Tip: Restart your AI client after adding the server so it picks up the new tools.


🧰 Development

Use just for everything β€” install, run, lint, and checks:

just             # see available commands
just fix         # auto-fix lint/format issues
just check-all   # full project check before you ship

Available Tools

3 tools
addC

Add two numbers Axcient way

Inputs: a (required), b. Returns: result

get_billable_usageA

Get billable usage report for specified date range If not provided, it'll return current month's usage data It returns list of client usage in the children field

Inputs: end_date, start_date. Returns: object

get_client_infoD

Get billable usage report for specified date range If not provided, it'll return current month's usage data

Inputs: client_id (required). Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.2/5.0

    Scored across 3 tools

    Disambiguation1/5

    Two tools (get_billable_usage and get_client_info) have identical descriptions, making them indistinguishable. The add tool is unrelated, but the overlap between the other two is severe.

    Naming Consistency2/5

    Naming pattern is inconsistent: 'add' does not follow the 'get_' prefix of the other tools. Additionally, get_client_info has a misleading name given its description duplicates get_billable_usage.

    Tool Count3/5

    3 tools is borderline low but could be acceptable for a very narrow domain. However, the duplication reduces effective count to 2, making the set feel incomplete.

    Completeness2/5

    The server's purpose is unclear, but the limited scope (addition and two identical usage reports) suggests significant gaps. No update, delete, or list operations for clients or usage data.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      Not graded
      maintenance
      Gives AI assistants direct access to Autotask PSA for searching tickets, creating time entries, managing companies, projects, and more via natural language.
      100
      Apache 2.0
    • A
      license
      B
      quality
      B
      maintenance
      Connects AI assistants to Big Red Cloud accounting data, allowing natural-language queries and controlled write operations with safety checks.
      100
      Apache 2.0