ceos/fastmcp
1
0
Fork 0
mirror of https://github.com/PrefectHQ/fastmcp.git synced 2026-08-23 22:14:18 +02:00
Code Issues Projects Releases Packages Wiki Activity

Fix broken documentation links (#2952)

Browse source
This commit is contained in:
Jeremiah Lowin 2026-01-19 23:17:29 -05:00 • committed by GitHub
commit 3df38584cf
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
69 changed files with 179 additions and 179 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/v2/patterns/cli.mdx
View file

@ -192,7 +192,7 @@ The `--skip-env` flag is useful when:
- You want to test the server without environment setup
</Note>
See [Server Configuration](/deployment/server-configuration) for detailed documentation on fastmcp.json.
See [Server Configuration](/v2/deployment/server-configuration) for detailed documentation on fastmcp.json.
#### MCP Configuration

4
docs/v2/patterns/tool-transformation.mdx
View file

@ -522,7 +522,7 @@ directly in the MCPConfig json file.
The `tools` section is a dictionary of tool names to tool configurations. Each tool configuration is a
dictionary of tool properties.
See the [MCPConfigTransport](/clients/transports#tool-transformation-with-fastmcp-and-mcpconfig) documentation for more details.
See the [MCPConfigTransport](/v2/clients/transports#tool-transformation-with-fastmcp-and-mcpconfig) documentation for more details.
## Output Schema Control
@ -698,7 +698,7 @@ This pattern provides several benefits:
- **Scalable**: Easily add new tools by wrapping additional client methods
### Adapting Remote or Generated Tools
This is one of the most common reasons to use tool transformation. Tools from remote MCP servers (via a [proxy](/servers/proxy)) or generated from an [OpenAPI spec](/integrations/openapi) are often too generic for direct use by an LLM. You can use transformation to create a simpler, more intuitive version for your specific needs.
This is one of the most common reasons to use tool transformation. Tools from remote MCP servers (via a [proxy](/v2/servers/proxy)) or generated from an [OpenAPI spec](/v2/integrations/openapi) are often too generic for direct use by an LLM. You can use transformation to create a simpler, more intuitive version for your specific needs.
### Chaining Transformations
You can chain transformations by using an already transformed tool as the parent for a new transformation. This lets you build up complex behaviors in layers, for example, first renaming arguments, and then adding validation logic to the renamed tool.