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

Merge pull request #385 from didier-durand/text-typos

Browse source 
Fixing various text typos
This commit is contained in:
Jeremiah Lowin 2025-05-09 11:33:11 -04:00 • committed by GitHub
commit a220d8afad
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
4 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/getting-started/installation.mdx
View file

@ -81,7 +81,7 @@ pytest
### Pre-Commit Hooks
FastMCP uses pre-commit to manage code quality, including formatting, linting, and type-safety. All PR's must pass the pre-commit hooks, which are run as a part of the CI process. To install the pre-commit hooks, run:
FastMCP uses pre-commit to manage code quality, including formatting, linting, and type-safety. All PRs must pass the pre-commit hooks, which are run as a part of the CI process. To install the pre-commit hooks, run:
```bash
uv run pre-commit install

4
docs/getting-started/quickstart.mdx
View file

@ -89,7 +89,7 @@ This lets us run the server with `python my_server.py`, using the default `stdio
<Tip>
Why do we need the `if __name__ == "__main__":` block?
Within the FastMCP ecosystem, this line may be unecessary. However, including it ensures that your FastMCP server runs for all users and clients in a consistent way and is therefore recommended as best practice.
Within the FastMCP ecosystem, this line may be unnecessary. However, including it ensures that your FastMCP server runs for all users and clients in a consistent way and is therefore recommended as best practice.
</Tip>
### Interacting with the Python server
@ -124,5 +124,5 @@ fastmcp run my_server.py:mcp
Note that FastMCP *does not* require the `__main__` block in the server file, and will ignore it if it is present. Instead, it looks for the server object provided in the CLI command (here, `mcp`). If no server object is provided, `fastmcp run` will automatically search for servers called "mcp", "app", or "server" in the file.
<Tip>
We pointed our client at the server file, which is recognized as a Python MCP server and executed with `python my_server.py` by default. This exceutes the `__main__` block of the server file. There are other ways to run the server, which are described in the [server configuration](/servers/fastmcp#running-the-server) guide.
We pointed our client at the server file, which is recognized as a Python MCP server and executed with `python my_server.py` by default. This executes the `__main__` block of the server file. There are other ways to run the server, which are described in the [server configuration](/servers/fastmcp#running-the-server) guide.
</Tip>

2
src/fastmcp/server/proxy.py
View file

@ -124,7 +124,7 @@ class ProxyTemplate(ResourceTemplate):
params: dict[str, Any],
context: Context | None = None,
) -> ProxyResource:
# dont use the provided uri, because it may not be the same as the
# don't use the provided uri, because it may not be the same as the
# uri_template on the remote server.
# quote params to ensure they are valid for the uri_template
parameterized_uri = self.uri_template.format(

2
src/fastmcp/server/server.py
View file

@ -892,7 +892,7 @@ class FastMCP(Generic[LifespanResultT]):
future changes to the imported server will not be reflected in the
importing server. Server-level configurations and lifespans are not imported.
When an server is mounted: - The tools are imported with prefixed names
When a server is mounted: - The tools are imported with prefixed names
using the tool_separator
Example: If server has a tool named "get_weather", it will be
available as "weatherget_weather"