my-tools

MCP server to make my detailed automation tools available to AI agents as well. private https://github.com/nishio/my-tools public https://github.com/nishio/my-tools-mcp-server-public-preview

2025-02-03 Create an MCP server $ mkdir my-tools $ code my-tools

add a tool As an experiment to call a local Python script, I'm going to make one that returns the current time when called.

Create MCP server $ npx @modelcontextprotocol/create-server time-server

Since you have already built the MCP server, the next step is to add a tool that calls a Python script to this server. Edit the server's configuration file to add a tool that calls the Python script. index.ts

{
  name: "get_current_time",
  description: "Get the current time",
  inputSchema: {
    type: "object",
    properties: {},
    required: []
  }
}

I see index.ts

server.setRequestHandler(CallToolRequestSchema, async (request) => {
  switch (request.params.name) {
    case "get_current_time": {
      const { execSync } = require('node:child_process');
      const output = execSync('python3 current_time.py').toString().trim();
      return {
        content: [{
          type: "text",
          text: `Current time is: ${output}`
        }]
      };
    }

    default:
      throw new Error("Unknown tool");
  }
});

I see

:

{
  "mcpServers": {
    "time-server": {
      "command": "node",
      "args": ["/Users/nishio/my-tools/time-server/build/index.js"],
      "env": {}
    }
  }
}

I am getting an error that the current_time.py script cannot be found. This is because the path to the script is not specified correctly; you need to specify the correct path when executing the script in execSync. The file is

I was able to do it!

Claude Desktop ready, able

Now that I understand the logic, I'll figure out what to do in the future. I don't want to have to create and configure a new server every time I make a small tool, so I'd like to have a server called my-tools, which is like a toolbox for all sorts of things.

$ npx @modelcontextprotocol/create-server mcp-server and move the time-retrieval function of time-server to mcp-server

I was able to do it.

I think it would be more productive for "me + AI agent" to make this MCP server dedicated to myself and verbalize my knowledge as code, such as "I put my papers here in Dropbox", instead of publishing and maintaining this MCP server as a generic "others use it too".

• People who use generic tools end up doing "highly abstract system descriptions" that customize those generic tools to their own situation.
• For my personal use, it's twice as hard to generalize it and then specialize it for myself.
• Currently, the script is also an absolute path including my username.
• So I pushed it to private repo.
• On the other hand, I don't have any specific confidential information at this time, so I've put that in a separate public disclosure.

This page is auto-translated from /nishio/my-tools using DeepL. If you looks something interesting but the auto-translated English is not good enough to understand it, feel free to let me know at @nishio_en. I'm very happy to spread my thought to non-Japanese readers.