ASD-STE100 Simplified Technical English

biz.dfch.AsdSte100Mcp

[ASD-STE100: Issue 9] [License: AGPL v3] [Python] [Lint and Test] [TestPyPI version] [PyPI version] [PyPI downloads] [MCP Registry] [Auth: none]

An MCP server for the ASD-STE100 (Simplified Technical English) Issue 9 standard.

ASD-STE100: Copyright by (c) ASD.

I am in no way affiliated with ASD. ASD does not endorse my work.

Table of Contents

• Tools
• Resources
• Installation
• Usage
• Authentication
• Add to OpenCode
• Development
• Related Projects
• Make a Release
• License

Authentication

This server exposes only read-only lookup tools and resources over vocabulary and rules data that is bundled with the package; there is nothing to authenticate against. No API keys, tokens, or credentials are required or supported in either stdio or sse transport mode. If you expose the sse transport beyond localhost, secure it at the network layer (e.g. a reverse proxy) rather than expecting the server to authenticate requests itself.

Tools

Vocabulary

Rules

Resources

Read-only resources let a client browse or attach ruleset data directly (e.g. via an "@mention" or resource picker), without going through a tool call.

Installation

pip install biz-dfch-asdste100mcp

Or with uv:

uv add biz-dfch-asdste100mcp

Usage

MCP Inspector

If you want to test the MCP server without a tool like OpenCode, you can do this with MCP Inspector.

MCP Inspector is part of the mcp[cli] package. When you install this project with --extra dev you can use MCP Inspector.

NOTE: The examples below use bunx instead of npx to launch MCP Inspector; npx has not been tested.

stdio (Claude Desktop, OpenCode, and other MCP hosts)

asdste100-mcp

Run MCP Inspector against the server over stdio:

bunx @modelcontextprotocol/inspector uv run --frozen --directory . asdste100-mcp

[MCP Inspector with stdio]

NOTE: Sometimes, the MCP Inspector cannot connect to the MCP server via stdio. Use the sse option (see below) instead.

SSE / network

asdste100-mcp --transport sse --host localhost --port 8000

NOTE: You do not have to supply the option --port to the MCP server. The default value of port is 8000.

Start the server, then connect MCP Inspector to it — these are two separate commands, run in two separate terminals:

# terminal 1: start the serveruvx --from . asdste100-mcp -t sse

# terminal 2: launch the inspector and connect it to the running serverbunx @modelcontextprotocol/inspector

[Start the MCP server with uvx and then start the MCP Inspector with bunx]

[MCP Inspector with sse]

Options

Vocabulary configuration

Rules configuration

Add to OpenCode

To add the ASD-STE100 (Simplified Technical English) MCP server to your OpenCode configuration:

1. Open your OpenCode config file (typically ~/.config/opencode/opencode.json or ~/.config/opencode/opencode.jsonc)

2. Add the following configuration to the mcp section (and use it via stdio):

"asdste100": {  "type": "local",  "enabled": true,  "command": ["uvx", "--from", "biz-dfch-asdste100mcp", "asdste100-mcp"]}

3. Save the file and restart OpenCode

This enables OpenCode to access ASD-STE100 vocabulary and rules lookups for technical writing and documentation compliance.

Development

Install dev dependencies

uv sync --all-extras

Run linters

uv run --frozen ruff format --checkuv run --frozen ruff checkuv run --frozen pylint $(git ls-files '*.py')

Run tests

uv run --frozen python -m unittest discover -v -s tests -t . -p "test_*.py"

Related Projects

This server is part of the ASD-STE100 tooling family:

• biz.dfch.AsdSte100Vocab — the ASD-STE100 Issue 9 vocabulary library
• biz.dfch.AsdSte100Rules — the ASD-STE100 Issue 9 ruleset library
• biz.dfch.AsdSte100Nlp — WordNet-based synonym lookup for ASD-STE100 words
• biz.dfch.AsdSte100Lookup — an interactive CLI to look up words and rules
• biz.dfch.AsdSte100Mcp — this repo: an MCP server exposing vocabulary and rules lookup tools

Make a Release

1. Make sure all tests pass

Before releasing, make sure the CI pipeline is green on the dev branch:

uv run --frozen ruff format --checkuv run --frozen ruff checkuv run --frozen pylint $(git ls-files '*.py')uv run --frozen python -m unittest discover -v -s tests -t . -p "test_*.py"

2. Increase the version

Update the version in pyproject.toml:

version = "x.y.z"

3. Commit and push to dev

git add pyproject.toml CHANGELOG.mdgit commit -m "chore: bump version to vx.y.z"git push origin dev

4. Merge dev into main

git checkout maingit merge devgit push origin main

5. Create and push a version tag

export VERSION=x.y.zgit tag v${VERSION}git push origin v${VERSION}

Pushing the tag triggers the publish.yml workflow, which will:

1. Build the sdist and wheel.
2. Publish to TestPyPI (environment testpypi).
3. Publish to PyPI (environment pypi), only if TestPyPI succeeded.
4. Publish to the MCP Registry (publish-to-mcp-registry job) — requires the new version to be live on PyPI first.
5. Create a GitHub Release with auto-generated notes and the distribution artifacts attached.

Then switch back to dev to continue work:

git checkout dev

Configure Trusted Publishing

The workflow uses OIDC Trusted Publishing — no API tokens or secrets are needed.

GitHub: create environments

Go to your repo → Settings → Environments and create two environments:

TestPyPI

Log in at test.pypi.org → Your account → Publishing → Add a new pending publisher:

PyPI

Log in at pypi.org → Your account → Publishing → Add a new pending publisher:

MCP Registry Publishing

The publish-to-mcp-registry job uses GitHub OIDC authentication and does not require additional setup — it will automatically publish to the official MCP Registry once the package is live on PyPI.

Verify your server is registered:

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.dfch/biz-dfch-asdste100mcp"

License

AGPL-3.0-or-later