api-to-mcp-forge 0.1.0__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- api_to_mcp_forge-0.1.0/.gitignore +13 -0
- api_to_mcp_forge-0.1.0/LICENSE +202 -0
- api_to_mcp_forge-0.1.0/NOTICE +5 -0
- api_to_mcp_forge-0.1.0/PKG-INFO +128 -0
- api_to_mcp_forge-0.1.0/README.md +95 -0
- api_to_mcp_forge-0.1.0/pyproject.toml +67 -0
- api_to_mcp_forge-0.1.0/src/api_to_mcp/__init__.py +6 -0
- api_to_mcp_forge-0.1.0/src/api_to_mcp/__main__.py +5 -0
- api_to_mcp_forge-0.1.0/src/api_to_mcp/cli.py +167 -0
- api_to_mcp_forge-0.1.0/src/api_to_mcp/server.py +2368 -0
- api_to_mcp_forge-0.1.0/src/api_to_mcp/workspace.py +111 -0
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
+
|
|
181
|
+
To apply the Apache License to your work, attach the following
|
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
+
replaced with your own identifying information. (Don't include
|
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
+
comment syntax for the file format. We also recommend that a
|
|
186
|
+
file or class name and description of purpose be included on the
|
|
187
|
+
same "printed page" as the copyright notice for easier
|
|
188
|
+
identification within third-party archives.
|
|
189
|
+
|
|
190
|
+
Copyright [yyyy] [name of copyright owner]
|
|
191
|
+
|
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
+
you may not use this file except in compliance with the License.
|
|
194
|
+
You may obtain a copy of the License at
|
|
195
|
+
|
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
+
|
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
+
See the License for the specific language governing permissions and
|
|
202
|
+
limitations under the License.
|
|
@@ -0,0 +1,128 @@
|
|
|
1
|
+
Metadata-Version: 2.5
|
|
2
|
+
Name: api-to-mcp-forge
|
|
3
|
+
Version: 0.1.0
|
|
4
|
+
Summary: Turn API documentation (a docs URL, OpenAPI/Swagger, Postman, RAML, WSDL, GraphQL, an HTML page or pasted text) into an MCP server: an evidence-only entry, tested and live-verified, served by platform-mcp-hub. MCP server, CLI and Claude Code plugin.
|
|
5
|
+
Project-URL: Homepage, https://github.com/tonyyang0504/api-to-mcp
|
|
6
|
+
Project-URL: Source, https://github.com/tonyyang0504/api-to-mcp
|
|
7
|
+
Project-URL: Issues, https://github.com/tonyyang0504/api-to-mcp/issues
|
|
8
|
+
Project-URL: Changelog, https://github.com/tonyyang0504/api-to-mcp/blob/main/CHANGELOG.md
|
|
9
|
+
Author: api-to-mcp contributors
|
|
10
|
+
License-Expression: Apache-2.0
|
|
11
|
+
License-File: LICENSE
|
|
12
|
+
License-File: NOTICE
|
|
13
|
+
Keywords: api,claude-code,code-generation,mcp,model-context-protocol,openapi,swagger
|
|
14
|
+
Classifier: Development Status :: 3 - Alpha
|
|
15
|
+
Classifier: Intended Audience :: Developers
|
|
16
|
+
Classifier: Operating System :: POSIX
|
|
17
|
+
Classifier: Programming Language :: Python :: 3
|
|
18
|
+
Classifier: Programming Language :: Python :: 3 :: Only
|
|
19
|
+
Classifier: Topic :: Software Development :: Code Generators
|
|
20
|
+
Requires-Python: >=3.10
|
|
21
|
+
Requires-Dist: httpx>=0.27
|
|
22
|
+
Requires-Dist: jsonschema>=4
|
|
23
|
+
Requires-Dist: mcp<3,>=2.2
|
|
24
|
+
Requires-Dist: platform-mcp-hub<0.2,>=0.1
|
|
25
|
+
Requires-Dist: pytest-asyncio>=0.23
|
|
26
|
+
Requires-Dist: pytest>=8
|
|
27
|
+
Requires-Dist: pyyaml>=6
|
|
28
|
+
Requires-Dist: respx>=0.21
|
|
29
|
+
Provides-Extra: dev
|
|
30
|
+
Requires-Dist: build; extra == 'dev'
|
|
31
|
+
Requires-Dist: ruff>=0.6; extra == 'dev'
|
|
32
|
+
Description-Content-Type: text/markdown
|
|
33
|
+
|
|
34
|
+
# api-to-mcp
|
|
35
|
+
|
|
36
|
+
Turn an API's documentation into a working MCP server. Give it a docs URL, an OpenAPI/Swagger file, a Postman
|
|
37
|
+
collection, RAML, WSDL, a GraphQL endpoint, an HTML reference page or pasted text; the model reads it and writes an
|
|
38
|
+
**evidence-only entry** (every tool cites the documented endpoint), and api-to-mcp runs the deterministic steps: lint,
|
|
39
|
+
run config, contract tests, a stdio smoke test in Python and TypeScript, and a live verification against the real API.
|
|
40
|
+
|
|
41
|
+
The result is not generated code. It is one JSON entry describing the API, which the runtime serves as an MCP server:
|
|
42
|
+
`api-to-mcp serve <category> <id>` (or `platform-mcp-hub serve --entry my_entry.json`). By default the entry is
|
|
43
|
+
**generic**: its tools are the API's own operations (from an OpenAPI/Swagger description, `draft_entry` writes them),
|
|
44
|
+
and the answer is passed through, with optional field selection. Any HTTP API qualifies.
|
|
45
|
+
|
|
46
|
+
> **Not published yet.** `api-to-mcp` and its runtime dependency are not on PyPI yet. Until they are, install from
|
|
47
|
+
> source (below); do not install the names from a registry.
|
|
48
|
+
|
|
49
|
+
## Three ways to use it
|
|
50
|
+
|
|
51
|
+
- **Claude Code plugin** (skill `/api-to-mcp`, the `api-to-mcp` agent and the MCP server together):
|
|
52
|
+
```bash
|
|
53
|
+
claude plugin marketplace add tonyyang0504/api-to-mcp
|
|
54
|
+
claude plugin install api-to-mcp@api-to-mcp
|
|
55
|
+
```
|
|
56
|
+
Then: `/api-to-mcp https://developer.example.com/openapi.json`, or ask the `api-to-mcp` agent. Needs `uv` on PATH.
|
|
57
|
+
- **Any MCP client**: `api-to-mcp mcp` (stdio) or `api-to-mcp mcp --http --port 8090`. Tools: `doctor`, `workspace`,
|
|
58
|
+
`catalog_search`, `catalog_get`, `template_entry`, `ingest_openapi`, `read_docs`, `draft_entry`, `save_entry`, `lint_entry`,
|
|
59
|
+
`generate_server`, `try_tool`, `test_server`, `live_verify` ([docs/TOOLS.md](docs/TOOLS.md)).
|
|
60
|
+
- **CLI**: every tool is a command: `api-to-mcp ingest <url>`, `api-to-mcp save jobs my_board entry.json`,
|
|
61
|
+
`api-to-mcp test jobs my_board`, `api-to-mcp serve jobs my_board`, ... (`api-to-mcp --help`).
|
|
62
|
+
|
|
63
|
+
## Quick start (from source, today)
|
|
64
|
+
|
|
65
|
+
```bash
|
|
66
|
+
git clone https://github.com/tonyyang0504/api-to-mcp && cd api-to-mcp
|
|
67
|
+
uv venv -p 3.12
|
|
68
|
+
uv pip install "platform-mcp-hub @ git+https://github.com/tonyyang0504/platform-mcp" -e .
|
|
69
|
+
.venv/bin/api-to-mcp doctor # prerequisites and where entries will be saved
|
|
70
|
+
.venv/bin/api-to-mcp ingest https://raw.githubusercontent.com/PokeAPI/pokeapi/master/openapi.yml --filter pokemon
|
|
71
|
+
.venv/bin/api-to-mcp draft https://raw.githubusercontent.com/PokeAPI/pokeapi/master/openapi.yml pokeapi \
|
|
72
|
+
--operations pokemon_list,pokemon_retrieve > draft.json # tools straight from the API's operations
|
|
73
|
+
# review the draft (the skill/agent does this), then:
|
|
74
|
+
.venv/bin/api-to-mcp save generic pokeapi draft.json && .venv/bin/api-to-mcp lint generic pokeapi
|
|
75
|
+
.venv/bin/api-to-mcp generate generic pokeapi # run config + a starting contract test (tests/test_pokeapi_python.py)
|
|
76
|
+
.venv/bin/api-to-mcp test generic pokeapi # lint + contract test + stdio smoke (both runtimes)
|
|
77
|
+
.venv/bin/api-to-mcp verify generic pokeapi --plan '{"args": {"pokemon_retrieve": {"id": "pikachu"}, "pokemon_list": {"limit": 5}}}'
|
|
78
|
+
claude mcp add pokeapi -- "$PWD/.venv/bin/api-to-mcp" serve generic pokeapi
|
|
79
|
+
```
|
|
80
|
+
|
|
81
|
+
Once published: `uvx --from api-to-mcp-forge api-to-mcp doctor`, `pip install api-to-mcp-forge`.
|
|
82
|
+
The PyPI package is `api-to-mcp-forge` (PyPI treats `api-to-mcp` as a duplicate of an older, unrelated `apitomcp`); the command is `api-to-mcp`.
|
|
83
|
+
|
|
84
|
+
## Where entries go
|
|
85
|
+
|
|
86
|
+
- **Your own workspace (default)**: `API_TO_MCP_HOME`, else `$XDG_DATA_HOME/api-to-mcp`, else
|
|
87
|
+
`~/.local/share/api-to-mcp`. Nothing else is needed: the vocabularies, the lint and the runtime are installed with
|
|
88
|
+
api-to-mcp. `generate_server` writes an MCP client config (`servers/<category>/<id>/mcp.json`).
|
|
89
|
+
- **Optional: a runtime checkout.** `API_TO_MCP_CHECKOUT=<checkout of the runtime's repository>` (or `--checkout <dir>`)
|
|
90
|
+
saves entries into that checkout's catalog, writes its registry metadata and runs its contract tests, for contributing
|
|
91
|
+
an entry upstream.
|
|
92
|
+
|
|
93
|
+
## What it will not do
|
|
94
|
+
|
|
95
|
+
Documentation is treated as untrusted data: api-to-mcp fetches only public hosts (every redirect re-checked, connections
|
|
96
|
+
pinned to the vetted address, downloads capped at 25 MB), reads local specs only from spec files outside hidden
|
|
97
|
+
directories, and never follows instructions found in a document. The agent has no shell and no free web fetch. Live
|
|
98
|
+
verification calls read tools only. See [SECURITY.md](SECURITY.md).
|
|
99
|
+
|
|
100
|
+
## Limits (honest list)
|
|
101
|
+
|
|
102
|
+
- **The model does the judgement.** Entry quality depends on the model reading the docs carefully; the gates catch
|
|
103
|
+
structural mistakes (unknown arguments, wrong result paths, schema violations), not every misreading.
|
|
104
|
+
- **What the runtime can express.** REST/JSON, form and XML bodies, SOAP, GraphQL over POST, RSS/Atom, CSV; auth by
|
|
105
|
+
header, query, basic, bearer, session login, OAuth2 client credentials and refresh tokens, HMAC and OAuth 1.0a
|
|
106
|
+
signing. No OAuth authorization-code flow in the server (you obtain the refresh token once), no WebSockets
|
|
107
|
+
(AsyncAPI is explained, not served), no file streaming beyond the documented upload verbs.
|
|
108
|
+
- **Generic answers are the API's own.** A generic tool returns what the API returns (narrowed by root and selected
|
|
109
|
+
fields, long lists cut at `max_items`); it does not normalise records across APIs. The optional category mode does,
|
|
110
|
+
for the categories its vocabularies cover.
|
|
111
|
+
- **Drafts need review.** `draft_entry` reads OpenAPI 3 and Swagger 2 only; it cannot know which POSTs merely read, which
|
|
112
|
+
parameters the live API ignores, or which of hundreds of operations you need. Other formats are written by hand.
|
|
113
|
+
- **Live checks need access.** Keyless APIs are verified live; others need your credentials, and write tools are never
|
|
114
|
+
called live.
|
|
115
|
+
- **TypeScript half.** Without node and platform-mcp-hub's TypeScript runtime the gates run Python only, and say so.
|
|
116
|
+
- **Unpublished.** Installation is from source until the first release.
|
|
117
|
+
|
|
118
|
+
## Built on
|
|
119
|
+
|
|
120
|
+
The runtime that serves entries, validates them and runs the checks is the `platform-mcp-hub` library
|
|
121
|
+
([platform-mcp](https://github.com/tonyyang0504/platform-mcp)), installed as an ordinary dependency.
|
|
122
|
+
|
|
123
|
+
How api-to-mcp was verified end to end, the defects found and the limits: [docs/VERIFICATION.md](docs/VERIFICATION.md).
|
|
124
|
+
|
|
125
|
+
## Contributing and licence
|
|
126
|
+
|
|
127
|
+
Contributions are welcome: see [CONTRIBUTING.md](CONTRIBUTING.md) (DCO sign-off) and the
|
|
128
|
+
[Code of Conduct](CODE_OF_CONDUCT.md). Changes: [CHANGELOG.md](CHANGELOG.md). Licence: Apache-2.0 (`LICENSE`, `NOTICE`).
|
|
@@ -0,0 +1,95 @@
|
|
|
1
|
+
# api-to-mcp
|
|
2
|
+
|
|
3
|
+
Turn an API's documentation into a working MCP server. Give it a docs URL, an OpenAPI/Swagger file, a Postman
|
|
4
|
+
collection, RAML, WSDL, a GraphQL endpoint, an HTML reference page or pasted text; the model reads it and writes an
|
|
5
|
+
**evidence-only entry** (every tool cites the documented endpoint), and api-to-mcp runs the deterministic steps: lint,
|
|
6
|
+
run config, contract tests, a stdio smoke test in Python and TypeScript, and a live verification against the real API.
|
|
7
|
+
|
|
8
|
+
The result is not generated code. It is one JSON entry describing the API, which the runtime serves as an MCP server:
|
|
9
|
+
`api-to-mcp serve <category> <id>` (or `platform-mcp-hub serve --entry my_entry.json`). By default the entry is
|
|
10
|
+
**generic**: its tools are the API's own operations (from an OpenAPI/Swagger description, `draft_entry` writes them),
|
|
11
|
+
and the answer is passed through, with optional field selection. Any HTTP API qualifies.
|
|
12
|
+
|
|
13
|
+
> **Not published yet.** `api-to-mcp` and its runtime dependency are not on PyPI yet. Until they are, install from
|
|
14
|
+
> source (below); do not install the names from a registry.
|
|
15
|
+
|
|
16
|
+
## Three ways to use it
|
|
17
|
+
|
|
18
|
+
- **Claude Code plugin** (skill `/api-to-mcp`, the `api-to-mcp` agent and the MCP server together):
|
|
19
|
+
```bash
|
|
20
|
+
claude plugin marketplace add tonyyang0504/api-to-mcp
|
|
21
|
+
claude plugin install api-to-mcp@api-to-mcp
|
|
22
|
+
```
|
|
23
|
+
Then: `/api-to-mcp https://developer.example.com/openapi.json`, or ask the `api-to-mcp` agent. Needs `uv` on PATH.
|
|
24
|
+
- **Any MCP client**: `api-to-mcp mcp` (stdio) or `api-to-mcp mcp --http --port 8090`. Tools: `doctor`, `workspace`,
|
|
25
|
+
`catalog_search`, `catalog_get`, `template_entry`, `ingest_openapi`, `read_docs`, `draft_entry`, `save_entry`, `lint_entry`,
|
|
26
|
+
`generate_server`, `try_tool`, `test_server`, `live_verify` ([docs/TOOLS.md](docs/TOOLS.md)).
|
|
27
|
+
- **CLI**: every tool is a command: `api-to-mcp ingest <url>`, `api-to-mcp save jobs my_board entry.json`,
|
|
28
|
+
`api-to-mcp test jobs my_board`, `api-to-mcp serve jobs my_board`, ... (`api-to-mcp --help`).
|
|
29
|
+
|
|
30
|
+
## Quick start (from source, today)
|
|
31
|
+
|
|
32
|
+
```bash
|
|
33
|
+
git clone https://github.com/tonyyang0504/api-to-mcp && cd api-to-mcp
|
|
34
|
+
uv venv -p 3.12
|
|
35
|
+
uv pip install "platform-mcp-hub @ git+https://github.com/tonyyang0504/platform-mcp" -e .
|
|
36
|
+
.venv/bin/api-to-mcp doctor # prerequisites and where entries will be saved
|
|
37
|
+
.venv/bin/api-to-mcp ingest https://raw.githubusercontent.com/PokeAPI/pokeapi/master/openapi.yml --filter pokemon
|
|
38
|
+
.venv/bin/api-to-mcp draft https://raw.githubusercontent.com/PokeAPI/pokeapi/master/openapi.yml pokeapi \
|
|
39
|
+
--operations pokemon_list,pokemon_retrieve > draft.json # tools straight from the API's operations
|
|
40
|
+
# review the draft (the skill/agent does this), then:
|
|
41
|
+
.venv/bin/api-to-mcp save generic pokeapi draft.json && .venv/bin/api-to-mcp lint generic pokeapi
|
|
42
|
+
.venv/bin/api-to-mcp generate generic pokeapi # run config + a starting contract test (tests/test_pokeapi_python.py)
|
|
43
|
+
.venv/bin/api-to-mcp test generic pokeapi # lint + contract test + stdio smoke (both runtimes)
|
|
44
|
+
.venv/bin/api-to-mcp verify generic pokeapi --plan '{"args": {"pokemon_retrieve": {"id": "pikachu"}, "pokemon_list": {"limit": 5}}}'
|
|
45
|
+
claude mcp add pokeapi -- "$PWD/.venv/bin/api-to-mcp" serve generic pokeapi
|
|
46
|
+
```
|
|
47
|
+
|
|
48
|
+
Once published: `uvx --from api-to-mcp-forge api-to-mcp doctor`, `pip install api-to-mcp-forge`.
|
|
49
|
+
The PyPI package is `api-to-mcp-forge` (PyPI treats `api-to-mcp` as a duplicate of an older, unrelated `apitomcp`); the command is `api-to-mcp`.
|
|
50
|
+
|
|
51
|
+
## Where entries go
|
|
52
|
+
|
|
53
|
+
- **Your own workspace (default)**: `API_TO_MCP_HOME`, else `$XDG_DATA_HOME/api-to-mcp`, else
|
|
54
|
+
`~/.local/share/api-to-mcp`. Nothing else is needed: the vocabularies, the lint and the runtime are installed with
|
|
55
|
+
api-to-mcp. `generate_server` writes an MCP client config (`servers/<category>/<id>/mcp.json`).
|
|
56
|
+
- **Optional: a runtime checkout.** `API_TO_MCP_CHECKOUT=<checkout of the runtime's repository>` (or `--checkout <dir>`)
|
|
57
|
+
saves entries into that checkout's catalog, writes its registry metadata and runs its contract tests, for contributing
|
|
58
|
+
an entry upstream.
|
|
59
|
+
|
|
60
|
+
## What it will not do
|
|
61
|
+
|
|
62
|
+
Documentation is treated as untrusted data: api-to-mcp fetches only public hosts (every redirect re-checked, connections
|
|
63
|
+
pinned to the vetted address, downloads capped at 25 MB), reads local specs only from spec files outside hidden
|
|
64
|
+
directories, and never follows instructions found in a document. The agent has no shell and no free web fetch. Live
|
|
65
|
+
verification calls read tools only. See [SECURITY.md](SECURITY.md).
|
|
66
|
+
|
|
67
|
+
## Limits (honest list)
|
|
68
|
+
|
|
69
|
+
- **The model does the judgement.** Entry quality depends on the model reading the docs carefully; the gates catch
|
|
70
|
+
structural mistakes (unknown arguments, wrong result paths, schema violations), not every misreading.
|
|
71
|
+
- **What the runtime can express.** REST/JSON, form and XML bodies, SOAP, GraphQL over POST, RSS/Atom, CSV; auth by
|
|
72
|
+
header, query, basic, bearer, session login, OAuth2 client credentials and refresh tokens, HMAC and OAuth 1.0a
|
|
73
|
+
signing. No OAuth authorization-code flow in the server (you obtain the refresh token once), no WebSockets
|
|
74
|
+
(AsyncAPI is explained, not served), no file streaming beyond the documented upload verbs.
|
|
75
|
+
- **Generic answers are the API's own.** A generic tool returns what the API returns (narrowed by root and selected
|
|
76
|
+
fields, long lists cut at `max_items`); it does not normalise records across APIs. The optional category mode does,
|
|
77
|
+
for the categories its vocabularies cover.
|
|
78
|
+
- **Drafts need review.** `draft_entry` reads OpenAPI 3 and Swagger 2 only; it cannot know which POSTs merely read, which
|
|
79
|
+
parameters the live API ignores, or which of hundreds of operations you need. Other formats are written by hand.
|
|
80
|
+
- **Live checks need access.** Keyless APIs are verified live; others need your credentials, and write tools are never
|
|
81
|
+
called live.
|
|
82
|
+
- **TypeScript half.** Without node and platform-mcp-hub's TypeScript runtime the gates run Python only, and say so.
|
|
83
|
+
- **Unpublished.** Installation is from source until the first release.
|
|
84
|
+
|
|
85
|
+
## Built on
|
|
86
|
+
|
|
87
|
+
The runtime that serves entries, validates them and runs the checks is the `platform-mcp-hub` library
|
|
88
|
+
([platform-mcp](https://github.com/tonyyang0504/platform-mcp)), installed as an ordinary dependency.
|
|
89
|
+
|
|
90
|
+
How api-to-mcp was verified end to end, the defects found and the limits: [docs/VERIFICATION.md](docs/VERIFICATION.md).
|
|
91
|
+
|
|
92
|
+
## Contributing and licence
|
|
93
|
+
|
|
94
|
+
Contributions are welcome: see [CONTRIBUTING.md](CONTRIBUTING.md) (DCO sign-off) and the
|
|
95
|
+
[Code of Conduct](CODE_OF_CONDUCT.md). Changes: [CHANGELOG.md](CHANGELOG.md). Licence: Apache-2.0 (`LICENSE`, `NOTICE`).
|
|
@@ -0,0 +1,67 @@
|
|
|
1
|
+
[project]
|
|
2
|
+
name = "api-to-mcp-forge"
|
|
3
|
+
version = "0.1.0"
|
|
4
|
+
description = "Turn API documentation (a docs URL, OpenAPI/Swagger, Postman, RAML, WSDL, GraphQL, an HTML page or pasted text) into an MCP server: an evidence-only entry, tested and live-verified, served by platform-mcp-hub. MCP server, CLI and Claude Code plugin."
|
|
5
|
+
readme = "README.md"
|
|
6
|
+
requires-python = ">=3.10"
|
|
7
|
+
license = "Apache-2.0"
|
|
8
|
+
license-files = ["LICENSE", "NOTICE"]
|
|
9
|
+
authors = [{ name = "api-to-mcp contributors" }]
|
|
10
|
+
keywords = ["mcp", "model-context-protocol", "openapi", "swagger", "api", "code-generation", "claude-code"]
|
|
11
|
+
classifiers = [
|
|
12
|
+
"Development Status :: 3 - Alpha",
|
|
13
|
+
"Intended Audience :: Developers",
|
|
14
|
+
"Operating System :: POSIX",
|
|
15
|
+
"Programming Language :: Python :: 3",
|
|
16
|
+
"Programming Language :: Python :: 3 :: Only",
|
|
17
|
+
"Topic :: Software Development :: Code Generators",
|
|
18
|
+
]
|
|
19
|
+
# platform-mcp-hub: the runtime, vocabularies, lint and verification the entries run on. The rest lets the gates run
|
|
20
|
+
# from this package's own environment: Swagger/OpenAPI YAML (pyyaml), the contract tests (pytest, pytest-asyncio,
|
|
21
|
+
# respx) and live verification's schema checks (jsonschema).
|
|
22
|
+
dependencies = [
|
|
23
|
+
"platform-mcp-hub>=0.1,<0.2",
|
|
24
|
+
"mcp>=2.2,<3",
|
|
25
|
+
"httpx>=0.27",
|
|
26
|
+
"pyyaml>=6",
|
|
27
|
+
"jsonschema>=4",
|
|
28
|
+
"pytest>=8",
|
|
29
|
+
"pytest-asyncio>=0.23",
|
|
30
|
+
"respx>=0.21",
|
|
31
|
+
]
|
|
32
|
+
|
|
33
|
+
[project.optional-dependencies]
|
|
34
|
+
dev = ["ruff>=0.6", "build"]
|
|
35
|
+
|
|
36
|
+
[project.scripts]
|
|
37
|
+
api-to-mcp = "api_to_mcp.cli:entry"
|
|
38
|
+
|
|
39
|
+
[project.urls]
|
|
40
|
+
Homepage = "https://github.com/tonyyang0504/api-to-mcp"
|
|
41
|
+
Source = "https://github.com/tonyyang0504/api-to-mcp"
|
|
42
|
+
Issues = "https://github.com/tonyyang0504/api-to-mcp/issues"
|
|
43
|
+
Changelog = "https://github.com/tonyyang0504/api-to-mcp/blob/main/CHANGELOG.md"
|
|
44
|
+
|
|
45
|
+
[build-system]
|
|
46
|
+
requires = ["hatchling>=1.26"]
|
|
47
|
+
build-backend = "hatchling.build"
|
|
48
|
+
|
|
49
|
+
[tool.hatch.build.targets.wheel]
|
|
50
|
+
packages = ["src/api_to_mcp"]
|
|
51
|
+
|
|
52
|
+
[tool.hatch.build.targets.sdist]
|
|
53
|
+
include = ["/src/api_to_mcp", "/README.md", "/LICENSE", "/NOTICE"]
|
|
54
|
+
exclude = ["**/__pycache__"]
|
|
55
|
+
|
|
56
|
+
[tool.pytest.ini_options]
|
|
57
|
+
asyncio_mode = "auto"
|
|
58
|
+
testpaths = ["tests"]
|
|
59
|
+
|
|
60
|
+
[tool.ruff]
|
|
61
|
+
line-length = 200
|
|
62
|
+
target-version = "py310"
|
|
63
|
+
extend-exclude = ["_platform-mcp"] # CI checks the runtime repository out here
|
|
64
|
+
|
|
65
|
+
[tool.ruff.lint]
|
|
66
|
+
select = ["E", "F", "W", "B"]
|
|
67
|
+
ignore = ["E501", "B008", "E731", "B904"]
|
|
@@ -0,0 +1,6 @@
|
|
|
1
|
+
"""api-to-mcp: turn API documentation (a docs URL, an OpenAPI/Swagger file, an HTML page, pasted text) into an MCP
|
|
2
|
+
server. The judgement (reading a platform's docs and writing an evidence-only entry) belongs to the model driving the
|
|
3
|
+
skill; the deterministic parts (templates, lint, run config, tests, live checks) are tools here, so any MCP client can
|
|
4
|
+
run them. Entries run with platform-mcp-hub (`platform-mcp-hub serve --entry <file>`)."""
|
|
5
|
+
|
|
6
|
+
__version__ = "0.1.0"
|