Repository navigation
Conversation
- notra's posts through its MCP server (mcp.usenotra.com), signed in to with OAuth or given an API key, declared once in BUILT_IN_MCP - one posts collection: list newest first and narrowed by type, open, create as a draft, edit title, slug and content, delete - publish and unpublish are commands behind their own high-risk Publish posts action, since a published post reaches the workspace's hosted site - the account is the workspace, from whoami, so a key for a connected workspace renews that connection - notra keeps a session and checks a key only when a tool is called, so the server does the handshake and the key check asks whoami - docs page, nav and index entry, and the logo
Collaborator
|
huh, looks like retargeting didn't work, github auto-closed the PR instead |
Collaborator
|
feel free to re-raise against main |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds Notra as a built-in integration, on top of #116's
BUILT_IN_MCP. People sign in through Notra's MCP server (mcp.usenotra.com, OAuth withopenid offline_access) or paste a Notra API key. Agents get a workspace's posts: blog posts, changelogs and social posts.whoamias "Name · slug". A key for a workspace that's already connected renews that connection, the same as signing in again.handshake: true. It also checks an API key only when a tool is called (it answersInvalid API keyas a failed tool), so the key check callswhoami, andtoolErrormaps that answer tocredentials_rejected.mcp.usenotra.comare taken over, and theirlist_posts,get_post,create_post,update_postanddelete_postsettings carry over.connections/notra, plus nav and index entries and the logo.This doesn't add generation, brand identities, schedules or GEO. Those tools stay in Notra.
Checked with
bun run typecheck,bun run test(one existing instructions string updated),bun run lintandbun run build. I haven't run a live sign-in against Notra yet.Base is
hkonsti/parallelai-vs-exa(#116). It retargets tomainonce that merges.