About Arknet
Arknet is an MCP server in the Browser category: dDD architectural models that machines can understand. W3C standards (RDF/OWL) rather than proprietary DSLs -- validatable (SHACL), queryable (SPARQL), AI-ready (MCP).
Install
From source
git clone https://github.com/kogn-io/arknetThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Tools (8)
req_addCreate a requirement (functional / non-functional), with one or more testable acceptance criteria, each its own positioned resource (`arkreq:AcceptanceCriterion`), and an optional `rationale` recording *why* the requirement exists (`arkreq:rationale`). Title, description, rationale and every criterion's text are natively multilingual -- an optional `language` argument tags the literals being written (BCP-47, e.g. `"en"`); omitted, it falls back to the project's configured default language, and rejects the call if the project has none either
Parameters not published.
req_getFetch a single requirement by identity (e.g. FR-1, NFR-7). An optional `displayLocale` argument picks which language variant of a multilingual title/description/rationale/acceptance-criterion text to return, falling back to the calling project's `defaultLanguage`, then to an untagged value
Parameters not published.
req_link_constraintLink a requirement to a constraint it is bound by (`oslc_rm:constrainedBy`; the constraint must already exist -- create it first with `constraint_add`). Linking the same constraint twice is a no-op
Parameters not published.
req_link_termLink a requirement to a glossary term (`arkreq:usesTerm`; the term must exist). Linking the same term twice is a no-op. To remove a link (or replace the whole set), use `req_update`'s `usesTermCodes` instead
Parameters not published.
req_listList all managed requirements
Parameters not published.
req_schemaThe `arkreq:` vocabulary (RequirementType, RequirementStatus, Priority) as data -- definition + allowed values, so a client need not guess
Parameters not published.
req_set_statusChange lifecycle status (PROPOSED / ACCEPTED)
Parameters not published.
req_updateCorrect a requirement's title, description, rationale and/or MoSCoW priority (each optional, unchanged if omitted -- and this is also how a requirement created without a rationale records one afterwards); append new acceptance criteria, correct an existing one's text by position, and/or remove one or more by position (the survivors renumber consecutively from 1) -- reordering is still not supported, and a position cannot be both corrected and removed in the same call. `usesTermCodes` replaces the requirement's `arkreq:usesTerm` links wholesale: omitted leaves them untouched, an empty list clears them all, a non-empty list is the full set going forward (kogn-io/arknet#540) -- `req_link_term` remains the convenient way to add a single link without restating the rest. `language` scopes a non-omitted title/description/rationale/touched-criterion write to that one language's literal (falling back to the project's default language if omitted, rejecting the call if neither is set), leaving other language variants untouched -- except a stale untagged one, swept away once the resolved tag equals the project's default. A project that maintains several languages gets a closing signal: the fields this call wrote that still carry another maintained language, put there by an earlier write and possibly out of date. A field that did not carry the written language yet is being translated, not corrected, and is never reported. It never blocks -- the remedy is to repeat the call under that language.
Parameters not published.
Ask AI
✦
Ask AI about Arknet
Powered by Claude · Grounded in docs
I know everything about Arknet. Ask me about installation, configuration, usage, or troubleshooting.
Security checks
6 checks have not been run yet.