Broader Frontends
Author : Kazuhiro Hara
Article permalink

Making Setup Easier: Seiro MCP v0.5.0 Released

Sometimes I wonder whether Seiro MCP is still necessary now that even Xcode has MCP. But from the perspective of autonomous coding, I think Seiro MCP has the advantage of being lightweight and easy to handle. In that sense, there is still plenty of room to improve it as a product, which led to this release. This update adds fixes and features with the stance of making setup as easy as possible.

In Seiro MCP v0.5.0, rather than increasing what it can do, I added features and reduced complexity from the viewpoint of making setup easier.

For people who wanted to try Seiro MCP at the "Engawa AI x XR" event, I tried installing it again myself from a completely clean environment. Because my memory of the process had faded in various places, it felt annoyingly complicated. I thought that was not a good state.

By the way, Seiro MCP is a support tool that provides functions essential for autonomous coding, such as building and retrieving errors when creating Vision Pro apps with Codex, so that AI can bring the app to a runnable state by itself. It is not exclusively for Codex, but I am first thinking about it running in a Codex environment. In fact, it can also create Mac apps and iOS apps, but in terms of my own support scope, I position it as being for visionOS.

However, in previous versions there were confusing parts in the initial setup, and this release makes those parts dramatically easier. The confusing parts were as follows.

  • Installing the MCP server is troublesome
  • You need to look up the absolute path of the seiro-mcp binary yourself
  • You need to create the project-side config.toml manually
  • Codex's ~/.codex/config.toml and the project-side config.toml are easy to confuse
  • Even for local use, MCP_SHARED_TOKEN looks necessary, and the fact that TCP can also be used adds complexity even though local use is the default

Previously, you had to do the initial setup while looking at the repository documentation. With this update, you can now generate most setup files automatically, or generate copy-and-paste templates, using the seiro-mcp command and its help.

New Feature 1: Output an MCP Server Configuration Template from the CLI

This feature may only be used once during setup, but at the beginning it is surprisingly easy to wonder what values should go into ~/.codex/config.toml.

So I added this feature.

$ seiro-mcp config mcp

When you run it, it outputs TOML that can be pasted directly into ~/.codex/config.toml, like this.

[mcp_servers.seiro_mcp]
command = "/Users/<user>/.cargo/bin/seiro-mcp"

Even if you install Seiro MCP with Cargo, you may wonder where it was installed. This reduces the need to look up the path with which seiro-mcp or rewrite example configuration.

New Feature 2: Automatically Generate the Project-Side Configuration File

Running the following from the project root now generates the minimum configuration for Seiro MCP.

$ seiro-mcp config project

Starting with this version, the configuration file is named seiro-mcp.toml rather than config.toml.

The reason is simple: the name config.toml easily collides with other tools and is also easy to confuse with Codex's ~/.codex/config.toml.

So from v0.5.0 onward, the structure is as follows.

  • ~/.codex/config.toml: Codex-side MCP server registration
  • /seiro-mcp.toml: Project-side Seiro MCP configuration

If an existing seiro-mcp.toml is present, it normally will not be overwritten. If you explicitly want to replace it, run:

$ seiro-mcp config project --force

New Feature 3: Skill Installation Is Simpler Too

Until now, skill installation was done like this.

$ seiro-mcp skill install seiro-mcp-visionos-build-operator

But currently there is only one skill, so this now works.

$ seiro-mcp skill install

There is also a --dry-run option.

seiro-mcp skill install --dry-run

Change: TCP Support and the Seiro MCP Usage Token Are Deprecated

Until now, there was TCP-based support for the MCP server, a feature that probably no one used, including me. Having this feature made the system more complex because it required settings such as usage tokens. I judged that it was unlikely to be used as a use case, so for now I have deprecated it. If requests come in later, such as wanting to use it in CI, I may consider it again, but for now it has been removed from the main path.

That is all. I think Seiro MCP has become much easier to use, so please continue to support it. Stars are also welcome.

visionOSCodexAI

Share

Back to Specials