FastMCP FastMCP
Sign In
A

Acemcp

Enables semantic code search across codebases with automatic incremental indexing. Searches return r...

5 views
0 installs
Updated Feb 1, 2026
Not audited
Developer Tools Coding
Tools I Recommend
ClaudeKit ClaudeKit Sponsor
Enables semantic code search across codebases with automatic incremental indexing. Searches return relevant code snippets with file paths and line numbers based on natural language queries.

  1. Decide which API you will use for indexing

    • If you are using Augment / ACE (Augment Context Engine), you need a tenant URL (API endpoint) and an access token. Otherwise, obtain the API endpoint and bearer token from the provider you plan to use. (github.com)

  2. Obtain an access token and tenant/API URL for Augment (if using Augment/ACE)

    • Install the Auggie CLI: 
      npm install -g @augmentcode/auggie@latest
    • Sign in interactively (opens a browser): 
      auggie login
    • Print the authentication token and tenant URL: 
      auggie token print
      • Copy the returned accessToken value (the bearer token) and the tenantURL (the API endpoint). (docs.augmentcode.com)

  3. Map the values required by acemcp

    • BASE_URL = your API endpoint (tenantURL / provider endpoint).
    • TOKEN = your bearer access token (accessToken).
    • Alternatively use environment variables with the ACEMCP_ prefix (recommended by the project): ACEMCP_BASE_URL and ACEMCP_TOKEN. (github.com)

  4. Open the FastMCP connection interface via the “Install Now” button

    • Click the ready-made “Install Now” button to open the FastMCP / MCP connection form (the place where environment variables and config for the MCP server are entered). (github.com)

  5. Fill the environment variables in the FastMCP connection interface

    • Add these entries (use whichever form your interface accepts—individual env fields or an env JSON block):
      • ACEMCP_BASE_URL = https://your-tenant-url-or-api-endpoint
      • ACEMCP_TOKEN = your-access-token
    • If the interface prefers the raw config JSON, add under env: 
      "env": {
  "ACEMCP_BASE_URL": "https://your-tenant-url-or-api-endpoint",
  "ACEMCP_TOKEN": "your-access-token"
}
    • (If you prefer not to use the ACEMCP_ prefix, you can set BASE_URL and TOKEN directly; command-line flags --base-url and --token will also override config.) (github.com)

  6. Save/apply and start (or restart) the MCP server

    • Save the connection settings in FastMCP, then start or restart the MCP server so it picks up the new environment variables.

  7. Verify the token & connectivity

    • If you enabled the acemcp Web management UI (start with --web-port), open the panel (e.g., http://localhost:8888) and use the Token validation / “检测 Key” button to verify the token is accepted by the configured BASE_URL. (github.com)

  8. Security reminder

    • Do not commit tokens to source control. Use the FastMCP environment fields or a secure secrets store and restrict access to users who need it. (github.com)

Quick Start

View on GitHub

More for Developer Tools

View All →

More for Coding

View All →

Similar MCP Servers

Report Issue

Thank you! Your issue report has been submitted successfully.