fix: console.info interfering with stdio, use stderr as recommended

[DaxServer]

Resolves #11

Summary by CodeRabbit

• Documentation

  • Updated the project description to clarify its focus on geocoding.

• Style

  • Improved formatting in configuration files for better readability.

• Chores

  • Adjusted logging output for server status messages.

[coderabbitai]

Walkthrough

This change updates the project description in package.json, adjusts a log statement in src/index.ts from console.info to console.error, and introduces blank lines for readability in tsconfig.json. No functional, dependency, or configuration semantics are altered.

Changes

Cohort / File(s)	Change Summary
Project Description Update package.json	Changed "description" field to "Model Context Protocol server for geocoding."
Logging Adjustment src/index.ts	Changed log output from console.info to console.error for server start message.
Formatting tsconfig.json	Added blank lines between compiler option groups for readability; no semantic changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Assessment against linked issues

Objective	Addressed	Explanation
Fix invalid JSON output from MCP server startup log (Claude Desktop startup issue) (#11)	✅

Poem

A hop, a skip, a tiny tweak,
The server’s log now springs a leak—
From info to error, a message anew,
The desktop starts up, the bug is through!
With tidy configs and a polished line,
This bunny says, “Your code is fine!” 🐇✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix-error-11

---

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 generate unit tests to generate unit tests for 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 (1)

src/index.ts (1)

21-21: Consider console.warn for non-error informational output
console.error routes to stderr (solving the stdio collision), but semantically denotes an error condition. Using console.warn keeps the same stderr stream while signalling that this is an informational start-up message, not a failure.

-  console.error('Geocoding API MCP Server running on stdio')
+  console.warn('Geocoding API MCP Server running on stdio')

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between fd13c4e and 00db23d.

⛔ Files ignored due to path filters (1)

• bun.lock is excluded by !**/*.lock

📒 Files selected for processing (3)

• package.json (1 hunks)
• src/index.ts (1 hunks)
• tsconfig.json (1 hunks)

🔇 Additional comments (2)

package.json (1)

5-5: Updated description accurately reflects the module’s purpose
The new wording clarifies that this package is a server implementation rather than a CLI. No functional impact detected.

tsconfig.json (1)

11-32: Whitespace-only change – no compiler-level impact
The added blank lines improve readability without altering any compiler options.