docs(recipes): add a recipe that connects MCPTool to the filesystem MCP server

[modelpath-dev]

• I have read and agree to the contributing guidelines.

Describe your changes

Adds a "Talk to Your Files with MCP" recipe under Recipes > Agents. It connects MCPTool to MCP's reference filesystem server (@modelcontextprotocol/server-filesystem over stdio, started with npx like the existing MCP tool example), limits the server to a temp folder of notes, prints the activities discovered from the server, and has an Agent read the notes and write a summary file back.

No new server is added, as suggested in the issue.

What I checked locally:

• Ran MCPTool against the live filesystem server: it discovered all 14 tools, and list_directory, read_text_file and write_file worked. Reading a path outside the allowed folder came back as an ErrorArtifact from the server.
• Built the OpenAI tool schemas for all 14 activities without errors.
• ruff format --check, ruff check, pyright, mdformat --check and typos pass on the new files, and mkdocs build --strict passes with the new page in the nav.
• tests/unit/tools/test_mcp_tool.py passes.

I did not run the Agent half against a live model key, so the code block test for this file will be its first full run in CI.

Issue ticket number and link

Closes #2306

---

📚 Documentation preview 📚: https://griptape--2377.org.readthedocs.build//2377/

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!