hana-developer-cli-tool-example: Instructions file for GitHub Copilot

.github/instructions/mcp-server-development.instructions.md

hana-developer-cli-tool-example mcp-server-development.instructions.md is an instructions file for GitHub Copilot from SAP-samples/hana-developer-cli-tool-example. It costs 4,811 tokens per session, scanned A, original, Apache-2.0.

Development rules for MCP servers. MCP, or Model Context Protocol, is a standard way for an AI agent to communicate with tools and data sources using structured messages.

In plain words
What is it for?
Use them when adding or changing MCP tools, resources, prompts, JSON-RPC message handling, schemas, or connections between the server and CLI commands.
Why use it?
They prevent protocol-breaking output and keep tool registration, data schemas, errors, and TypeScript code consistent. In particular, accidental logs sent to the wrong channel can break communication.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is SAP-samples/hana-developer-cli-tool-example's own configuration. It tells GitHub Copilot how to work on hana-developer-cli-tool-example itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything hana-developer-cli-tool-example configures →

Reuse

Borrowing it

Nothing to install: this file belongs to SAP-samples/hana-developer-cli-tool-example. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/SAP-samples/hana-developer-cli-tool-example/main/.github/instructions/mcp-server-development.instructions.md
Clone the repo
git clone --depth 1 https://github.com/SAP-samples/hana-developer-cli-tool-example

Made for: GitHub Copilot.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for hana-developer-cli-tool-example mcp-server-development.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/sap-samples/hana-developer-cli-tool-example/mcp-server-development/github.svg)](https://agentmods.dev/instructions/sap-samples/hana-developer-cli-tool-example/mcp-server-development)
Your own site
<a href="https://agentmods.dev/instructions/sap-samples/hana-developer-cli-tool-example/mcp-server-development"><img src="https://agentmods.dev/badge/instructions/sap-samples/hana-developer-cli-tool-example/mcp-server-development/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for hana-developer-cli-tool-example mcp-server-development.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/sap-samples/hana-developer-cli-tool-example/mcp-server-development"><img src="https://agentmods.dev/badge/instructions/sap-samples/hana-developer-cli-tool-example/mcp-server-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 4,811 This file is loaded in full into every session.
When invoked 4,811 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.04811 $0.04811
Opus 5.5 $0.01924 $0.01924
Sonnet 5.5 $0.00962 $0.00962
Haiku 4.5 $0.00481 $0.00481

Measured 1mo ago against content hash d6e7da98b2b7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

hana-developer-cli-tool-example mcp-server-development.instructions.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.github/instructions/mcp-server-development.instructions.md · 742 lines

How it starts

The opening of the file, as written. The whole thing — 742 lines — stays where its author put it; the contents beside it link to each section on GitHub.

MCP Server Development Guidelines

Use this guide when creating or modifying TypeScript files in the mcp-server/src/ directory.

Scope and Purpose

This guide applies to all TypeScript files implementing the Model Context Protocol (MCP) server that exposes hana-cli commands as MCP tools, resources, and prompts for LLM consumption.

Critical Principles

  1. JSON-RPC Protocol Compliance: MCP communicates via JSON-RPC over STDIO
  2. Logging Discipline: ONLY use console.error() for logging, NEVER console.log()
  3. Tool Naming: Sanitize tool names to [a-z0-9_-] character set only
  4. Schema Generation: Convert yargs builders to JSON Schema accurately
  5. Error Enrichment: Provide actionable error analysis and suggestions
  6. Type Safety: Use TypeScript interfaces and explicit typing throughout
  7. CLI Integration: Maintain consistency with CLI command metadata and structure

CRITICAL: Logging Rules

NEVER write to stdout using console.log() - it will break the JSON-RPC protocol.

// ❌ WRONG - Breaks MCP protocol
console.log('Debug info:', data);
console.log(JSON.stringify(result));

// ✅ CORRECT - Write to stderr
console.error('[MCP Debug]', data);
console.error('[MCP Info]', JSON.stringify(result));

Why: MCP clients expect ONLY JSON-RPC messages on stdout. Any other output causes parsing failures like "Failed to parse message: ...".

Apply to:

  • The main index.ts file header comment documents this
  • All imported modules that might log (executor.ts, command-parser.ts, etc.)
  • Error handling and debugging code

File Structure and Organization

Main Entry Point: index.ts

#!/usr/bin/env node

/**
 * MCP Server for SAP HANA CLI
 * 
 * CRITICAL: This file implements the Model Context Protocol (MCP) server.
 * MCP communicates via JSON-RPC over STDIO. All logging MUST use console.error()
 * to write to stderr, never console.log() which writes to stdout.
 */

import { Server } from '@modelcontextprotocol/sdk/server/index.js';
import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';
// ... more imports

class HanaCliMcpServer {
  private server: Server;
  private commands: Map<string, any> = new Map();

  constructor() {
    this.server = new Server(
      {
        name: 'hana-cli-mcp-server',
        version: '1.0.0',
        icons: [/* icon configuration */],
      },
      {
        capabilities: {
          tools: {},
          resources: {},
          prompts: {},
        },
      }
    );

    this.setupHandlers();
    this.setupErrorHandling();
  }

  private setupHandlers(): void {
    // Register handlers for tools, resources, prompts
  }

  private setupErrorHandling(): void {
    this.server.onerror = (error) => {
      console.error('[MCP Error]', error);
    };

    process.on('SIGINT', async () => {
      await this.server.close();
      process.exit(0);
    });
  }

  async run(): Promise<void> {
    const transport = new StdioServerTransport();
    await this.server.connect(transport);
    console.error('[MCP Server] Running on stdio');
  }
}

const server = new HanaCliMcpServer();
server.run().catch(console.error);

Read the full file on GitHub · 742 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 742 lines · 4,811 tokens per session scan A d6e7da98b2b7

Subscribe to this mod's changes

hana-developer-cli-tool-example mcp-server-development.instructions.md is an instructions file published in the GitHub repository SAP-samples/hana-developer-cli-tool-example (114 stars, last pushed 11d ago), licensed Apache-2.0. It adds 4,811 tokens to every session, about $0.0192 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,649 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,549 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens