The flow is explicit rather than templated: create_server, then add_tool and add_resource one at a time, then generate_server_code to read what that adds up to before save_server commits it. Nothing here runs a server or reads an existing one back in, and configurations exist in memory until saved, so the generator is a starting point rather than a place to keep a project. create_example_server is the quickest way to see the shape it expects.
An eight-tool generator that holds server configurations in memory and emits complete Python code for them.
- A server configuration created with a name, version and description, then extended one addition at a time
- Tools added with a full signature: parameters, return_type, an implementation body and an is_async flag
- Resources added with a uri, mime_type and implementation, including template resources through is_template
- Complete Python code generated for a configuration, with or without comments, and written out by save_server under a filename you choose
- list_servers and get_server_details to see what is currently held, and create_example_server for a working configuration to start from
A writable path for save_server and a Python environment to run what it generates. No account and no key. Configurations are held in memory, so anything not saved is gone when the process ends. MIT licensed.
One command — uvx mcp-server-creator