Instead of having a persistent tab bar, could we (1) use the logo as the link to the "Overview" page, and (2) put the "Documentation" and "Community" links in the top nav bar?

Also, I feel like the sidebar for the Documentation tab is a bit overwhelming, as in "What is all this? Where am I supposed to look?" The /documentation/index page seems like it might be used to provide an overview of all of the items in the sidebar, which I think is good. But reducing the number of immediately visible items might also be helpful (e.g. by adding more collapsed-by-default groups).

Instead of having a persistent tab bar, could we (1) use the logo as the link to the "Overview" page, and (2) put the "Documentation" and "Community" links in the top nav bar?

Also, I feel like the sidebar for the Documentation tab is a bit overwhelming, as in "What is all this? Where am I supposed to look?" The /documentation/index page seems like it might be used to provide an overview of all of the items in the sidebar, which I think is good. But reducing the number of immediately visible items might also be helpful (e.g. by adding more collapsed-by-default groups).

Thanks! Good ideas, will check if this is possible with Mintlify.

Also this is still very much a placeholder, definitely not final. Just creating this for folks to "work into" sooner rather than later.

@jonathanhefner I had a look and unfortunately it looks like the navbar up top only supports hrefs, not relative links (see docs: https://mintlify.com/docs/settings#param-navbar):

❯ npm run serve:docs

> @modelcontextprotocol/specification@0.1.0 serve:docs
> cd docs && mintlify dev

⠋ Preparing local Mintlify instance...🚨 Invalid docs.json:
#.navbar.links[1].href: Must be a valid url
✖ Prebuild step failed

Also, with the proposal to have Specification be its own tab as seen in #909 it might get quite crowded in that area anyway?

I had a look and unfortunately it looks like the navbar up top only supports hrefs, not relative links (see docs: https://mintlify.com/docs/settings#param-navbar):

It seems like that might a bug in the https://mintlify.com/docs.json schema. According to https://mintlify.com/docs/settings#param-href-1 (emphasis mine):

URL or path for the link destination.

Perhaps we could submit a ticket to Mintlify. (I would recommend an Anthropic employee be the one do so; the last time I submitted a ticket on Anthropic's behalf, customer support suggested incorrect solutions, and then closed the ticket when I requested escalation.)

As a workaround we could hard code the domain as https://modelcontextprotocol.io. Obviously, that would not adapt to local development though.