DocsTools & Configuration

Tools & Configuration

Tools are the capabilities your MCP server exposes to clients. Each tool represents an API operation that connected AI models and applications can invoke.

How Tools Are Generated

When you upload an OpenAPI specification during server creation, MCPForest parses the spec and automatically generates tool definitions. Each tool maps to an API operation and includes:

  • Name — Generated from the operation ID or path
  • Description — Pulled from the OpenAPI operation summary or description
  • HTTP Method — GET, POST, PUT, PATCH, DELETE, etc.
  • Path — The API endpoint path
  • Parameters — Extracted from the request schema

Managing Tools

After tools are generated, the Tools page lets you fine-tune which ones your server exposes:

Enable / Disable

Toggle individual tools on or off. Only enabled tools are available on the deployed server.

Select All / Deselect All

Quickly enable or disable all tools at once.

Rename

Change a tool's name to something more descriptive. Good tool names help AI models choose the right tool.

Search

Filter tools by name to quickly find specific ones in large specs.

Tool Display

On the server detail page, each tool displays its HTTP method badge (color-coded: blue for GET, green for POST, amber for PUT, red for DELETE) alongside the path and description. This makes it easy to see at a glance what your server exposes.

API Authentication

During server creation, you can configure how MCPForest authenticates with your backing API. Currently supported:

  • None — No authentication (for public APIs)
  • Basic Auth — Username and password credentials sent with each request to your API

Best Practices

Use descriptive names

Tool names help AI models decide which tool to use. Rename generic names like "endpoint_1" to something meaningful like "get_user_profile."

Disable unused tools

Only enable the tools your use case requires. Fewer tools means less noise for AI models and more focused behavior.

Keep your OpenAPI spec clean

Well-documented OpenAPI specs produce better tool definitions. Include descriptions and clear parameter names in your spec for best results.