Update fastah-ip-geo-tools plugin with latest changes from Fastah repo 🤖🤖🤖#1194
Update fastah-ip-geo-tools plugin with latest changes from Fastah repo 🤖🤖🤖#1194punit-fastah wants to merge 1 commit intogithub:stagedfrom
Conversation
There was a problem hiding this comment.
Pull request overview
This PR adds an MCP server configuration to the fastah-ip-geo-tools plugin so the plugin can connect to Fastah’s IP Geofeed MCP endpoint.
Changes:
- Added
plugins/fastah-ip-geo-tools/.mcp.jsondefining an HTTP MCP server pointing athttps://mcp.fastah.ai/mcp.
| @@ -0,0 +1,8 @@ | |||
| { | |||
| "mcpServers": { | |||
| "fastahIpGeofeed": { | |||
There was a problem hiding this comment.
The MCP server key is named fastahIpGeofeed, but the geofeed-tuner skill documentation/examples reference the server as fastah-ip-geofeed. If agents/skills are written to target the documented server name, this config won’t be picked up and MCP tool calls will fail. Align the server name here with the name used by the skill (or update the skill docs/usage to match this name) so the configuration is discoverable.
| "fastahIpGeofeed": { | |
| "fastah-ip-geofeed": { |
|
I can't find any docs about the MCP server and I'm feeling like this is getting very close to the line on our policy regarding paid services. |
Hello @aaronpowell , the MCP server key in the The MCP server this is a free, non-commercial MCP service for geocoding RFC 8805 style place names - it's usage is explained in the SKILL.md. How do we document it so it's aligned in letter and spirit with the policy? Thank you in advance! |
This pull request adds a new file,
.mcp.json, for thefastah-ip-geo-tools plugin, specifying an MCP server endpoint, as described in the Visual Studio Code documentation: https://code.visualstudio.com/docs/copilot/customization/agent-plugins#_mcp-configuration-formatConfiguration update:
.mcp.jsonfile to theplugins/fastah-ip-geo-toolsdirectory, defining thefastahIpGeofeedMCP server with its type and URL.