chore: update mcp readme

[hande-k]

Description

DCO Affirmation

I affirm that all code in every commit of this pull request conforms to the terms of the Topoteretes Developer Certificate of Origin.

[pull-checklist]

Please make sure all the checkboxes are checked:

• I have tested these changes locally.
• I have reviewed the code changes.
• I have added end-to-end and unit tests (if applicable).
• I have updated the documentation and README.md file (if necessary).
• I have removed unnecessary code and debug statements.
• PR title is clear and follows the convention.
• I have tagged reviewers or team members for feedback.

[coderabbitai]

Walkthrough

The README.md for the cognee MCP server was updated to include a link to external documentation and a new "Running the Server" section. This section provides explicit instructions for starting the server using both stdio and SSE transport modes, detailing the specific commands to use for each.

Changes

File(s)	Change Summary
cognee-mcp/README.md	Added external documentation link and a "Running the Server" section with stdio and SSE instructions.

Possibly related PRs

• Add Smithery to README #399: Also updates cognee-mcp/README.md with new installation and server running instructions.
• Add mcp to cognee #370: Adds the MCP server implementation and entry points, providing context for the new running instructions.

Suggested reviewers

• dexters1
• borisarzentar

Poem

In README fields where docs now grow,
New commands for servers show.
Stdio or SSE, pick your way—
Just follow the guide, you won’t go astray!
🐇✨

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

cognee-mcp/README.md (2)

76-76: Remove trailing colon in heading
MarkdownLint (MD026) flags trailing punctuation in headings. Consider changing ### Standard stdio transport: to ### Standard stdio transport.

🧰 Tools

🪛 markdownlint-cli2 (0.17.2)

76-76: Trailing punctuation in heading
Punctuation: ':'

(MD026, no-trailing-punctuation)

---

81-81: Remove trailing colon in heading
MarkdownLint (MD026) flags trailing punctuation in headings. Consider changing ### SSE transport: to ### SSE transport.

🧰 Tools

🪛 markdownlint-cli2 (0.17.2)

81-81: Trailing punctuation in heading
Punctuation: ':'

(MD026, no-trailing-punctuation)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 88f8aee and d50e4d3.

📒 Files selected for processing (1)

• cognee-mcp/README.md (2 hunks)

🧰 Additional context used

🪛 markdownlint-cli2 (0.17.2)

cognee-mcp/README.md

76-76: Trailing punctuation in heading
Punctuation: ':'

(MD026, no-trailing-punctuation)

---

81-81: Trailing punctuation in heading
Punctuation: ':'

(MD026, no-trailing-punctuation)

⏰ Context from checks skipped due to timeout of 90000ms (10)

• GitHub Check: End-to-End Tests / S3 Bucket Test
• GitHub Check: End-to-End Tests / Deletion Test
• GitHub Check: End-to-End Tests / Deduplication Test
• GitHub Check: End-to-End Tests / Run Telemetry Test
• GitHub Check: End-to-End Tests / Run Telemetry Pipeline Test
• GitHub Check: End-to-End Tests / Server Start Test
• GitHub Check: Basic Tests / Run Simple Examples
• GitHub Check: Basic Tests / Run Basic Graph Tests
• GitHub Check: Basic Tests / Run Integration Tests
• GitHub Check: Basic Tests / Run Unit Tests

🔇 Additional comments (4)

cognee-mcp/README.md (4)

3-3: Add reference to external documentation
Good inclusion of a direct link to the MCP deployment guide for users needing more details.

---

74-74: Introduce "Running the Server" section
Clear separation of runtime instructions helps users get started quickly.

---

78-78: Include code block command
Command is clear and correctly formatted in a bash code block.

---

83-83: Include SSE transport command
Instruction is concise and correctly formatted; this covers the alternate transport mode.